| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Seeding database requires gitlab-shell, and we would like to avoid
adding this dependency to the CI.
|
|
|
|
|
|
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
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
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ruby 2.1.8 is used only on master for now, as this would give
confidance in case this commit has to be reverted.
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
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]
|
|
|
|
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.
|
|
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
|
|
Accidentally removed when !3807 was merged.
|
|
|
|
|
|
|
|
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.
|
|
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
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
