- 09 5月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 08 5月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 06 4月, 2017 3 次提交
-
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Lin Jen-Shin 提交于
whenever the feature is disabled in the project.
-
- 05 4月, 2017 8 次提交
-
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
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
-
- 28 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 16 3月, 2017 1 次提交
-
-
由 Z.J. van de Weg 提交于
-
- 22 2月, 2017 1 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
- 15 12月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
-
- 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.
-
- 18 7月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
Manual actions are accessible from: - Pipelines - Builds - Environments - Deployments
-