gitlab-org--gitlab-foss/.gitlab-ci.yml

image: "dev.gitlab.org:5005/gitlab/gitlab-build-images:ruby-2.5.3-golang-1.11-git-2.18-chrome-71.0-node-10.x-yarn-1.12-postgresql-9.6-graphicsmagick-1.3.29"

variables:
  MYSQL_ALLOW_EMPTY_PASSWORD: "1"
  RAILS_ENV: "test"
  NODE_ENV: "test"
  SIMPLECOV: "true"
  GIT_DEPTH: "20"
  GIT_SUBMODULE_STRATEGY: "none"
  GET_SOURCES_ATTEMPTS: "3"
  KNAPSACK_RSPEC_SUITE_REPORT_PATH: knapsack/${CI_PROJECT_NAME}/rspec_report-master.json
  FLAKY_RSPEC_SUITE_REPORT_PATH: rspec_flaky/report-suite.json
  BUILD_ASSETS_IMAGE: "false"

before_script:
  - bundle --version
  - date
  - source scripts/utils.sh
  - date
  - source scripts/prepare_build.sh
  - date

after_script:
  - date

stages:
  - build
  - prepare
  - merge
  - test
  - post-test
  - pages
  - post-cleanup

include:
  - local: .gitlab/ci/global.gitlab-ci.yml
  - local: .gitlab/ci/cng.gitlab-ci.yml
  - local: .gitlab/ci/docs.gitlab-ci.yml
  - local: .gitlab/ci/frontend.gitlab-ci.yml
  - local: .gitlab/ci/pages.gitlab-ci.yml
  - local: .gitlab/ci/qa.gitlab-ci.yml
  - local: .gitlab/ci/reports.gitlab-ci.yml
  - local: .gitlab/ci/rails.gitlab-ci.yml
  - local: .gitlab/ci/review.gitlab-ci.yml
  - local: .gitlab/ci/setup.gitlab-ci.yml
  - local: .gitlab/ci/test-metadata.gitlab-ci.yml
Bump CI image to use Chrome 71.0 and Golang 1.11 2019-01-06 10:52:09 -05:00			`image: "dev.gitlab.org:5005/gitlab/gitlab-build-images:ruby-2.5.3-golang-1.11-git-2.18-chrome-71.0-node-10.x-yarn-1.12-postgresql-9.6-graphicsmagick-1.3.29"`
More docker stuff in gitlab-ci.yml 2016-01-22 08:45:34 -05:00
			`variables:`
			`MYSQL_ALLOW_EMPTY_PASSWORD: "1"`
Use build stage 2016-05-21 21:41:17 -04:00			`RAILS_ENV: "test"`
Refactor test_utils bundle 2017-04-04 13:47:12 -04:00			`NODE_ENV: "test"`
Use build stage 2016-05-21 21:41:17 -04:00			`SIMPLECOV: "true"`
Use GIT_DEPTH when running builds 2016-06-17 04:59:48 -04:00			`GIT_DEPTH: "20"`
Submodule Dockerfile templates 2017-04-26 11:57:44 -04:00			`GIT_SUBMODULE_STRATEGY: "none"`
add new runner script attempts docs and update .gitlab-ci.yml 2016-12-15 06:40:33 -05:00			`GET_SOURCES_ATTEMPTS: "3"`
Don't include branch name in Knapsack report file Otherwise, branches other than master won't benefit from Knapsack! Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-03-28 04:12:37 -04:00			`KNAPSACK_RSPEC_SUITE_REPORT_PATH: knapsack/${CI_PROJECT_NAME}/rspec_report-master.json`
Improve the flaky examples detection jobs Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-10-04 07:24:51 -04:00			`FLAKY_RSPEC_SUITE_REPORT_PATH: rspec_flaky/report-suite.json`
Add BUILD_ASSETS_IMAGE CI variable * Defaults to FALSE * Can be used to disable building/pushing the assets image in the gitlab:compile:assets job 2018-11-14 12:36:02 -05:00			`BUILD_ASSETS_IMAGE: "false"`
More docker stuff in gitlab-ci.yml 2016-01-22 08:45:34 -05:00
Refactor CI script Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2015-06-04 10:54:32 -04:00			`before_script:`
Test 2016-05-22 01:31:38 -04:00			`- bundle --version`
Add date calls in .gitlab-ci.yml to see how long each step take Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-10-17 07:00:10 -04:00			`- date`
Resolve "rspec_profiling is enabled for MySQL" 2017-04-28 14:05:39 -04:00			`- source scripts/utils.sh`
Add date calls in .gitlab-ci.yml to see how long each step take Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-10-17 07:00:10 -04:00			`- date`
Resolve "rspec_profiling is enabled for MySQL" 2017-04-28 14:05:39 -04:00			`- source scripts/prepare_build.sh`
Add date calls in .gitlab-ci.yml to see how long each step take Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-10-17 07:00:10 -04:00			`- date`

			`after_script:`
			`- date`
updated gitlab-ci script to include builds URL 2016-02-24 16:53:13 -05:00
Try to use knapsack 2016-05-21 21:17:15 -04:00			`stages:`
Leverage the new cache policies in .gitlab-ci.yml Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-07-19 10:01:33 -04:00			`- build`
			`- prepare`
Automatically merge CE master into EE master This sets up GitLab CI to automatically push CE master changes into EE master, or revert them if the changes cause merge conflicts. The CI configuration contains a single job to do this: `merge:master`. This job is executed for every push to master, and periodically using a CI schedule. The periodic job is necessary because incremental jobs may not be able to revert commits if newly added commits depend on these commits. By re-running the job periodically (including all changes since a large enough time frame), we can ensure that such commits are also reverted (if they still conflict at that time). The job runs in its own "merge" stage, _after_ the build and prepare stages, but _before_ running the tests. This ensures that randomly failing tests won't prevent code from being merged into EE. Running the stage after the "prepare" stage reduces the chances of the job reverting CE changes just because it ran before a corresponding EE MR was merged into EE master. 2018-11-29 10:10:23 -05:00			`- merge`
Leverage the new cache policies in .gitlab-ci.yml Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-07-19 10:01:33 -04:00			`- test`
			`- post-test`
			`- pages`
Add script and job to trigger a docs build 2017-09-07 11:43:20 -04:00			`- post-cleanup`
updated gitlab-ci script to include builds URL 2016-02-24 16:53:13 -05:00
Refactor .gitlab-ci.yml 2019-04-12 04:56:38 -04:00			`include:`
			`- local: .gitlab/ci/global.gitlab-ci.yml`
			`- local: .gitlab/ci/cng.gitlab-ci.yml`
			`- local: .gitlab/ci/docs.gitlab-ci.yml`
			`- local: .gitlab/ci/frontend.gitlab-ci.yml`
			`- local: .gitlab/ci/pages.gitlab-ci.yml`
			`- local: .gitlab/ci/qa.gitlab-ci.yml`
			`- local: .gitlab/ci/reports.gitlab-ci.yml`
			`- local: .gitlab/ci/rails.gitlab-ci.yml`
			`- local: .gitlab/ci/review.gitlab-ci.yml`
			`- local: .gitlab/ci/setup.gitlab-ci.yml`
			`- local: .gitlab/ci/test-metadata.gitlab-ci.yml`