- 18 Jul, 2016 8 commits
-
-
Annabel Dunstone authored
-
Annabel Dunstone authored
- 17 Jul, 2016 1 commit
-
-
Annabel Dunstone authored
-
- 16 Jul, 2016 1 commit
-
-
Annabel Dunstone authored
-
- 14 Jul, 2016 16 commits
-
-
Lin Jen-Shin authored
So it's more accessible for views to access the names of jobs. Only filter Build#name from where we really need to download it.
-
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
It doesn't make too much sense having this standalone
-
Lin Jen-Shin authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5142#note_13058785 And note that job/build_name could contain `/`
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 13 Jul, 2016 6 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Basically: GET /api/projects/:id/artifacts/:ref_name/:build_name Also added tests for it.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 12 Jul, 2016 8 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
It turns out they are different: builds.success.latest.first and builds.latest.success.first If we put success first, that latest would also filter via success, and which is what we want here.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-