- 06 Apr, 2017 4 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Not only tracking auto-cancelling in pipelines, we'll also track this in jobs because pipelines could be retried and the information would get lost when this happened. Also erase auto-cancelling relation for pipelines when they're retried.
-
- 05 Apr, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Mike Wyatt authored
-
- 04 Apr, 2017 4 commits
-
-
Rydkin Maxim authored
-
Rydkin Maxim authored
-
Rydkin Maxim authored
-
Rydkin Maxim authored
fix changelog MR reference add non-HEAD builds finder and add `created` pipelines to scope add spec for auto-cancel non-HEAD pipelines and refactor create_pipeline_service_spec more refactoring for spec adds option for auto-cancel into CI/CD settings fix spec to new configuration fix rubocop fix schema.rb fix schema.rb replace Gitlab 9.0 with 9.1 in doc change wording on pipeline settings added auto_canceled_by field as identifier of autocancel subject remove unnecessary index replace service with retry_lock replace auto_cancel_pending_pipelines boolean setting with integer (and enum in model) fix schema.rb fix schema.rb remove projekt attribute and clean up spec clean up spec withcouple of shared examples added spec for "It does not cancel current pipeline" scenario add some specs to auto-cancel add spec for another branch pipelines
-
- 03 Apr, 2017 1 commit
-
-
Sean McGivern authored
1. Never send a pipeline email to anyone other than the user who created the pipeline. 2. Only send pipeline success emails to people with the custom notification setting for enabled. Watchers and participants will never receive this. 3. When custom settings are unset (for new settings and legacy ones), act as if failed_pipeline is set.
-
- 02 Apr, 2017 1 commit
-
-
Stan Hu authored
From Bullet failures in !10263
-
- 20 Mar, 2017 2 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
In APIv1 we've been sending all jobs from previous stages and a `dependencies` list with names of jobs that user want to download artifacts from. This was selected on Runners side. In APIv1 we've planned to send only jobs that were defined (if any; and all previous jobs by default). However I've missed the fact that it was Runner who selected jobs, not GitLab. And now current version of APIV4 sends all jobs everytime. This commit fixes this. If user will define `dependencies` in his job, then GitLab will send only selected jobs.
-
- 17 Mar, 2017 1 commit
-
-
Kamil Trzciński authored
-
- 16 Mar, 2017 4 commits
-
-
Tiago Botelho authored
-
Bob Van Landuyt authored
This could happen when the repository is missing. In which case cache needs to be cleared
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
This reads status from redis & stores it in redis if it was missing. If the project has no HEAD, the cache is deleted
-
- 08 Mar, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 07 Mar, 2017 4 commits
-
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
Given GitLab moves away from using the term build, everywhere, also the CI variables are being renamed. For now, both `CI_BUILD_X` and `CI_JOB_X` are supported, with the same values. However, in about 3 months, support will be dropped.
-
Kamil Trzciński authored
-
Tomasz Maczukin authored
-
- 06 Mar, 2017 9 commits
-
-
Tomasz Maczukin authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 05 Mar, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- they can have owner, - they can be edited, - they have description, - you can take ownership of them
-
- 03 Mar, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 02 Mar, 2017 2 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 01 Mar, 2017 1 commit
-
-
Grzegorz Bizon authored
-