- 20 Jul, 2016 24 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
So we no longer join anything, just find the latest pipeline and load builds from there to avoid mixing builds. Thanks Kamil for the help and tests.
-
Lin Jen-Shin authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5347#note_13195683 and https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5347#note_13195692 another_artifacts was no longer used and then there's no point to put let in outer scope anymore.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
this should properly test that it's really getting the builds from the latest successful pipelines and latest successful builds.
-
Lin Jen-Shin authored
also added a test for checking this.
-
Lin Jen-Shin authored
rubocop was complaining
-
Lin Jen-Shin authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5347#note_13176921 Also we give undesired builds another artifacts so that we could tell if returned artifacts was we actual expected.
-
- 19 Jul, 2016 16 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Merge remote-tracking branch 'upstream/artifacts-from-ref-and-build-name-api-kamil' into artifacts-from-ref-and-build-name-api * upstream/artifacts-from-ref-and-build-name-api-kamil: Make minimal changes to specs
-
Kamil Trzcinski authored
-
Lin Jen-Shin authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5347/diffs#note_13173336 let! is not very flexible but I guess it's fine since this is not in top-level anyway.
-
Lin Jen-Shin authored
-