- 06 Dec, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
Pass `updated_at` to get only incremental changes since last update
-
- 22 Nov, 2016 1 commit
-
- 26 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 24 Oct, 2016 1 commit
-
-
David Wagner authored
They were Rails' default and are unnecessarily overridden. Signed-off-by: David Wagner <david@marvid.fr>
-
- 12 Oct, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 08 Oct, 2016 3 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 07 Oct, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 06 Oct, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 04 Oct, 2016 7 commits
-
-
Lin Jen-Shin authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 03 Oct, 2016 5 commits
-
-
Lin Jen-Shin authored
-
Kamil Trzcinski authored
Conflicts: app/models/ci/pipeline.rb app/models/commit_status.rb
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
which merges previous exclude_ignored_jobs and failed_but_allowed, so that we don't treat ignored a special case in HasStatus.
-
- 19 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
This solves Pipelines in `running` after all stages do finish.
-
- 14 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 12 Sep, 2016 3 commits
-
-
Lin Jen-Shin authored
This reverts commit 575dc2b0.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Because pipeline status could be changed for the builds in the next stages, if we process next stages first, the current build would be out of synchronized, and would need a reload for that matter. Alternatively, like what I did in this commit, we could process the next stages later (by using `after_transition` rather than `around_transition`), and complete what're doing for the current build first. This way we don't have to reload because nothing is out synchronized. Note that since giving `false` in `after_transition` would halt the callbacks chain, according to: https://github.com/state-machines/state_machines-activemodel/blob/v0.4.0/lib/state_machines/integrations/active_model.rb#L426-L429 We'll need to make sure we're not returning false because we don't intend to interrupt the chain. This fixes #22010. After this fix, both pipeline events and build events would only show up once.
-
- 07 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 25 Aug, 2016 2 commits
-
-
Paco Guzman authored
-
De Wet Blomerus authored
-
- 18 Aug, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 15 Aug, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 12 Aug, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 11 Aug, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-