BigW Consortium Gitlab

  1. 29 Aug, 2017 1 commit
  2. 01 Aug, 2017 1 commit
  3. 20 Jul, 2017 1 commit
  4. 02 Jun, 2017 1 commit
  5. 01 Jun, 2017 2 commits
  6. 06 Apr, 2017 1 commit
  7. 31 Mar, 2017 1 commit
  8. 20 Mar, 2017 2 commits
    • 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.
  9. 07 Mar, 2017 1 commit
  10. 02 Mar, 2017 10 commits
  11. 28 Feb, 2017 1 commit
  12. 16 Feb, 2017 2 commits