summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* Remove Flog as we use a Rubocop that does its job.cs-remove-flog-flayConnor Shea2016-09-281-3/+0
|
* Limit test environment size to one project in CIGrzegorz Bizon2016-09-231-2/+2
|
* Improve CI job that tests database seedsGrzegorz Bizon2016-09-221-4/+4
|
* Try cloning repositories before seeding databaseGrzegorz Bizon2016-09-221-0/+2
| | | | | Seeding database requires gitlab-shell, and we would like to avoid adding this dependency to the CI.
* Add artifacts with development log when seed failsGrzegorz Bizon2016-09-221-0/+5
|
* Add development environment database setup CI testGrzegorz Bizon2016-09-221-6/+16
|
* Allow flay and flog to fail for nowStan Hu2016-09-141-2/+6
|
* Add haml_lint rake taskRémy Coutable2016-09-131-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Use haml_lint for views lintingRémy Coutable2016-09-131-0/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Merge branch 'enable-rspec-formatter' into 'master' Kamil Trzciński2016-09-081-1/+1
|\ | | | | | | | | | | | | Enable rspec documentation formatter and color output Current rspec just outputs a `=` as each test runs. This enables the documentation formatter and color output to make it easier to know what is going on with each spec. See merge request !5924
| * Add color to rspec outputenable-rspec-formatterStan Hu2016-08-201-1/+1
| |
| * Enable rspec documentation formatterStan Hu2016-08-201-1/+1
| |
* | Have CI test migration pathsZ.J. van de Weg2016-09-061-1/+15
|/ | | | | | | | | This commit adds a job to the pipeline to test if migration on seed data works. Even though the seed data is not perfect, it does give more guarentees that this will succeed in the real world too. seed_fu is used instead of dev:setup to save some time, as they both generate the data in the same way, this should be fine.
* Install latest stable phantomjsKamil Trzcinski2016-08-131-1/+1
|
* Use new PhantomJS versionKamil Trzcinski2016-08-131-0/+1
|
* Update ruby 2.3.1ruby-2-3-1Z.J. van de Weg2016-08-121-2/+2
|
* Update gitlab ci tests to test ruby 2.1 now tooZ.J. van de Weg2016-08-111-1/+1
|
* Default build tests ruby 2.3.1Z.J. van de Weg2016-08-111-40/+40
| | | | | Ruby 2.1.8 is used only on master for now, as this would give confidance in case this commit has to be reverted.
* Merge branch 'api-examples-curl-long-options' into 'master' Achilleas Pipinellis2016-08-101-0/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use long options for curl examples in documentation ## What does this MR do? Use long options (e.g. `--header` instead of `-H`) for curl examples in documentation. ## Why was this MR needed? Short options are less readable. ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5465#note_13603730 See merge request !5703
| * add linting script for documentationwinniehell2016-08-091-0/+7
| |
* | Add test coverage analysis for CoffeeScript (!5052)winniehell2016-08-071-0/+10
|/
* Don't setup DB for slack notification buildRuben Davila2016-08-041-0/+3
|
* Deploy test coverage report on master pipeline onlyGrzegorz Bizon2016-07-221-0/+2
|
* Improve CI configuration file for pages stageGrzegorz Bizon2016-07-221-6/+6
|
* Deploy ruby test coverage report to gitlab pagesGrzegorz Bizon2016-07-211-14/+29
|
* Fix SimpleCov report mergingKamil Trzcinski2016-07-211-1/+2
|
* Update configuration of SimpleCovKamil Trzcinski2016-07-211-0/+1
|
* Store all simplecov configuration in one fileKamil Trzcinski2016-07-211-0/+4
|
* Fix update-coverage jobKamil Trzcinski2016-07-211-1/+4
|
* Use `scripts/merge-simplecov`Kamil Trzcinski2016-07-211-1/+1
|
* Merge coverage reportKamil Trzcinski2016-07-211-0/+11
|
* Merge branch 'faster-builds-ci' into 'master' Douwe Maan2016-07-201-7/+28
|\ | | | | | | | | | | | | | | | | Speed improvement for builds without DB Only fetch the images which we are going to use. Speeds up the builds by about 30-45 seconds. /cc @ayufan See merge request !4994
| * Use YAML inheritance to DRY the .gitlab-ci.ymlfaster-builds-ciZ.J. van de Weg2016-07-201-19/+14
| |
| * Speed improvement for builds without DBZ.J. van de Weg2016-06-291-8/+34
| | | | | | | | | | | | Now the builds which do not use the DB or Redis won't pull the images from docker, and won't migrate the DB. This _should_ improve the build times slightly but also create a cleaner trace.
* | Added checks for migration downtimemigration-downtime-tagsYorick Peterse2016-07-201-1/+2
|/ | | | | | | | | | | These new checks can be used to check if migrations require downtime or not (as tagged by their authors). In CI this compares the current branch with master so migrations added by merge requests are automatically verified. To check the migrations added since a Git reference simply run: bundle exec rake gitlab:db:downtime_check[GIT_REF]
* Merge branch 'use-git-depth' into 'master' Kamil Trzciński2016-06-281-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use GIT_DEPTH for builds ## What does this MR do? Enables experimental feature to use shallow cloning. ## Why was this MR needed? To speed up the builds and reduce the pressure on NFS servers. This should save us between 30s to 1m of the time of each build. ## More information `GIT_DEPTH`: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/188 ## Problems - Too small value for `GIT_DEPTH` can make it impossible to retry old changes. You will see `unresolved reference` in build log. We should then reconsider changing `GIT_DEPTH` to higher value - Mechanism that rely on `git describe` may not work correctly when `GIT_DEPTH` is set. This will happen, because only part of the git history is present on the build machine ## Requirements GitLab Runner 1.3.0. Currently all our internal runners use beta release or 1.3.0 with support for `GIT_DEPTH`. @pcarranza Please decide when to merge that. We should start monitoring to see an impact on our NFS servers. cc @jacobvosmaer-gitlab @pcarranza See merge request !4730
| * Use GIT_DEPTH when running buildsuse-git-depthKamil Trzcinski2016-06-171-0/+1
| |
* | Add caching for Ruby 2.3 tests.Connor Shea2016-06-221-0/+5
| | | | | | | | Accidentally removed when !3807 was merged.
* | Add master-only limitation.Connor Shea2016-06-171-2/+2
| |
* | Remove branch restriction.Connor Shea2016-06-151-2/+2
| |
* | Upgrade Ruby 2.2 tests to 2.3connorshea2016-06-151-43/+38
|/ | | | | | | | | | | | | | This changes the GitLab CI Tests that test compatibility with Ruby 2.2 to instead test compat with Ruby 2.3. We’ve discussed skipping straight to 2.3.0 when next upgrading the required Ruby version. Since Rails 5 requires 2.2.2, and we have to upgrade anyway, may as well do it now and not risk having to upgrade again come Rails 5.1 or 5.2. Test failures on Ruby 2.3 do not fail the build.
* Merge branch 'retry-spinach-tests' into 'master' Rémy Coutable2016-06-141-3/+1
|\ | | | | | | | | | | | | | | | | | | Retry spinach tests in case of failure using rerun reporter ## What does this MR do? Fixes Spinach tests to retry on tests on master See merge request !4539
| * Use bundle exec to run spinachKamil Trzcinski2016-06-101-1/+1
| |
| * Merge remote-tracking branch 'origin/master' into retry-spinach-testsKamil Trzcinski2016-06-101-0/+2
| |\
| * | Retry spinach tests in case of failure using rerun reporterKamil Trzcinski2016-06-081-3/+1
| | |
* | | Cache only apt and ruby from vendorcache-apt-and-ruby-onlyKamil Trzcinski2016-06-121-1/+2
| |/ |/| | | | | | | Since introduction of gitignore the vendor folder contains also gitignores which affects detection when to update a cache. We explicitly cache only apt and ruby folders.
* | Update Knapsack report only on masterKamil Trzcinski2016-06-081-0/+2
|/
* Fix knapsack for masterknapsack-for-masterKamil Trzcinski2016-06-071-1/+1
|
* Remove stage notifications [ci skip]Kamil Trzcinski2016-06-071-1/+0
|
* Fix knapsack spinach executionKamil Trzcinski2016-06-071-1/+1
|
View Lorry Controller Status