- 07 4月, 2017 6 次提交
-
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Toon Claes 提交于
Enable caching in the Etag::Middleware and when a pipeline changes status, expire the cache for the project pipelines path.
-
- 06 4月, 2017 3 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
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.
-
由 Lin Jen-Shin 提交于
-
- 03 4月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
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.
-
- 17 3月, 2017 1 次提交
-
-
由 Tiago Botelho 提交于
-
- 16 3月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 08 3月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 06 3月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 23 2月, 2017 3 次提交
-
-
由 Douwe Maan 提交于
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 15 2月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 14 2月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 13 2月, 2017 3 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 27 1月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 18 1月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 27 12月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 26 12月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 24 12月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
This reverts merge request !8286
-
- 23 12月, 2016 2 次提交
-
-
由 Lin Jen-Shin 提交于
Feedback from Grzegorz
-
由 Lin Jen-Shin 提交于
The name latest implies that it's reverse chronological, and we did expect it that way. https://gitlab.com/gitlab-org/gitlab-ce/issues/25993#note_20429761 > ok, I think markglenfletchera is correct in > https://gitlab.com/gitlab-com/support-forum/issues/1394#note_20399939 > that `Project#latest_successful_builds_for` is giving oldest pipeline > rather than latest pipeline. This is a ~regression introduced by !7333 > where `order(id: :desc)` was removed causing this. The offending change > was: > https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7333/diffs#b22732e5f39e176c7c719fe485847d0fb0564275_92_108 > > The confusion was caused by the `latest` name implication, which > actually didn't order anything, and I think we should add `order(id: > :desc)` to `Ci::Pipeline.latest` otherwise it's confusing that it's not > actually ordered. Closes #25993
-
- 21 12月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 20 12月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
- 15 12月, 2016 2 次提交
-
- 14 12月, 2016 1 次提交
- 12 12月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
[ci skip]
-
- 06 12月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-