Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
G
Game Library
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Game Development
Game Library
Commits
5447ddbf
Commit
5447ddbf
authored
3 years ago
by
Joseph Walton-Rivers
Committed by
Joseph Walton-Rivers
3 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add gitlab CI file.
This is a merged commit of a bunch of typos and whatnot.
parent
eaf7aff0
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#2995
failed
3 years ago
Changes
1
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+44
-0
44 additions, 0 deletions
.gitlab-ci.yml
with
44 additions
and
0 deletions
.gitlab-ci.yml
0 → 100644
+
44
−
0
View file @
5447ddbf
# This file is a template, and might need editing before it works on your project.
# To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
# This is a sample GitLab CI/CD configuration file that should run without any modifications.
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
# it uses echo commands to simulate the pipeline execution.
#
# A pipeline is composed of independent jobs that run scripts, grouped into stages.
# Stages run in sequential order, but jobs within stages run in parallel.
#
# For more information, see: https://docs.gitlab.com/ee/ci/yaml/README.html#stages
image
:
${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/alpine:latest
stages
:
# List of stages for jobs, and their order of execution
-
build
-
test
-
deploy
build-job
:
# This job runs in the build stage, which runs first.
stage
:
build
script
:
-
apk update && apk --update add g++ build-base cmake bash libstdc++
-
mkdir build && cd build
-
cmake ..
-
make
unit-test-job
:
# This job runs in the test stage.
stage
:
test
# It only starts when the job in the build stage completes successfully.
script
:
-
apk update && apk --update add g++ build-base cmake bash libstdc++ clang-tidy
-
mkdir build && cd build
-
cmake .. && make
# TODO cache build from previous step
-
./tests/testfggl/fggl_test
#lint-test-job: # This job also runs in the test stage.
# stage: test # It can run at the same time as unit-test-job (in parallel).
# script:
# - echo "Linting code... This will take about 10 seconds."
# - sleep 10
# - echo "No lint issues found."
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment