- 05 Apr, 2017 1 commit
-
-
Lin Jen-Shin authored
-
- 20 Mar, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 06 Mar, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 18 Jan, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 06 Dec, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 21 Nov, 2016 2 commits
-
- 18 Nov, 2016 1 commit
-
- 03 Oct, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 25 Aug, 2016 1 commit
-
-
De Wet Blomerus authored
-
- 27 Apr, 2016 1 commit
-
-
Grzegorz Bizon authored
This status will be returned only when there are no failed jobs that are not allowed to fail.
-
- 16 Apr, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 13 Apr, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 12 Apr, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 17 Mar, 2016 1 commit
-
-
Geoffrey Lalonde authored
-
- 20 Feb, 2016 1 commit
-
-
Grzegorz Bizon authored
Additional specs cover a case when one of the builds is running but allowed to fail. Previous implementation returned `running` status, which is wrong. This behavior has been changed in 8.5, this commit adds missing specs.
-
- 19 Feb, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 18 Feb, 2016 2 commits
-
-
Grzegorz Bizon authored
Before this fix when there was only one relevant, previous build and it failed, but was allowed to fail, entire build had been marked as skipped. Closes #3192
-
Grzegorz Bizon authored
-