- 30 5月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 11 5月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 06 3月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
This makes it possible to maintain backwards compatibility with configs created when manual actions were non-blocking. From now manual actions are blocking if configured with `allow_failure: false`, otherwise manual actions are optional, and their status is ignored.
-
- 01 3月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
-
- 23 2月, 2017 4 次提交
-
-
由 Douwe Maan 提交于
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-
由 Douwe Maan 提交于
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 25 1月, 2017 4 次提交
-
-
由 Leandro Camargo 提交于
-
由 Leandro Camargo 提交于
Instead of using: `coverage: /\(\d+.\d+%\) covered/` This structure must be used now: ``` coverage: output_filter: /\(\d+.\d+%\) covered/` ``` The surrounding '/' is optional.
-
由 Leandro Camargo 提交于
This commit: * Turns `coverage_regex` into `coverage` entry in yml file * Fixes smaller requests from code reviewers for the previous commit * This commit is temporary (will be squashed afterwards) This commit does not (further commits will do though): * Add global `coverage` entry handling in yml file as suggested by Grzegorz * Add specs * Create changelog * Create docs
-
由 Leandro Camargo 提交于
* Instead of using the proposed `coverage` key, this expects `coverage_regex`
-
- 19 12月, 2016 1 次提交
- 15 12月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
So that this would be more consistent with the other variables, which all of them are string based. Closes #25554
-
- 14 11月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 18 10月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 30 9月, 2016 2 次提交
-
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
- 19 9月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 07 9月, 2016 5 次提交
-
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
- 29 8月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 11 8月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
This change simplifies a Pipeline processing by introducing a special new status: created. This status is used for all builds that are created for a pipeline. We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped). This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled. This also allows us to visualise a full pipeline (with created builds). This also removes an after_touch used for updating a pipeline state parameters. Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
-
- 20 7月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 19 7月, 2016 4 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Grzegorz Bizon 提交于
-
- 18 7月, 2016 5 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Kamil Trzcinski 提交于
-