BigW Consortium Gitlab

  1. 28 Aug, 2017 1 commit
  2. 09 Aug, 2017 1 commit
  3. 02 Aug, 2017 1 commit
  4. 05 Jul, 2017 1 commit
  5. 21 Jun, 2017 1 commit
  6. 14 Jun, 2017 1 commit
  7. 12 Jun, 2017 2 commits
  8. 21 Apr, 2017 1 commit
  9. 06 Apr, 2017 1 commit
  10. 05 Apr, 2017 1 commit
  11. 20 Mar, 2017 5 commits
    • Send only defined dependencies · c191c110
      Tomasz Maczukin authored
      In APIv1 we've been sending all jobs from previous stages and
      a `dependencies` list with names of jobs that user want to download
      artifacts from. This was selected on Runners side.
      
      In APIv1 we've planned to send only jobs that were defined (if any; and
      all previous jobs by default). However I've missed the fact that
      it was Runner who selected jobs, not GitLab. And now current version
      of APIV4 sends all jobs everytime.
      
      This commit fixes this. If user will define `dependencies` in his job,
      then GitLab will send only selected jobs.
    • Send token of depenent job · 9267a9b1
      Tomasz Maczukin authored
      Artifacts download for authorization is using a job token of job to
      which the artifact belongs. In APIv1 the token was sent with dependent
      jobs details and in APIv4 it was designed to also contain it.
      
      However I forgot about this parameter while working on
      `/api/v4/jobs/request` endpoint.
      
      This commit adds a missing parameter which is required for APIv4 to work
      properly.
    • Remove legacy Runners support in /api/v4/jobs/request · e79ab111
      Tomasz Maczukin authored
      In Runner v1.3.0 we've started to send User-Agent header with Runner's
      version data. Since GitLab v8.12.0 we've started to use this header to check
      if used Runner's version supports 204 status code instead of 404 as a
      response when there is no jobs to execute by a Runner.
      
      In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And
      writing more accurately: GitLab Runner v9.0.0 will require GitLab at
      least 9.0.0. Because of such breaking change we are able to switch
      entirely to 204 response code and there is no need to do check of
      User-Agent.
      
      This commit removes useless code and complexity.
    • Make runner's veryfication working again · bbf4d27a
      Tomasz Maczukin authored
      In APIv1 we were using UpdateJob to verify if the runner exists. It was
      the only method that was using Runner's token and used in special way
      had no side effects (like scheduling a new job or unregisterring a
      Runner).
      
      In APIv4 we've change UpdateJob to use job's token as authentication
      credentials, and that way we've removed the only endpoint that could
      be used to verify if the Runner with a certain token exists in target
      GitLab installation.
      
      This commit adds `POST /api/v4/runners/verify` endpoint whose only
      responsibility is to respond if Runner with posted credentials exists or
      not.
  12. 16 Mar, 2017 1 commit
  13. 13 Mar, 2017 1 commit
  14. 07 Mar, 2017 1 commit
  15. 06 Mar, 2017 2 commits
  16. 02 Mar, 2017 11 commits
  17. 28 Feb, 2017 1 commit
  18. 16 Feb, 2017 3 commits