1. 12 Jul, 2019 1 commit
  2. 24 Feb, 2019 1 commit
  3. 24 Jan, 2019 1 commit
  4. 30 Sep, 2018 1 commit
  5. 07 Jun, 2018 1 commit
  6. 06 Apr, 2018 2 commits
  7. 28 Feb, 2018 1 commit
  8. 04 Feb, 2018 1 commit
  9. 02 Feb, 2018 1 commit
  10. 29 Jan, 2018 2 commits
  11. 28 Jan, 2018 1 commit
  12. 16 Nov, 2017 1 commit
  13. 18 Sep, 2017 2 commits
  14. 31 Aug, 2017 1 commit
    • Sean McGivern's avatar
      `current_application_settings` belongs on `Gitlab::CurrentSettings` · e1c28a485974
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
      e1c28a485974
  15. 28 Jun, 2017 1 commit
  16. 31 Mar, 2017 1 commit
  17. 20 Mar, 2017 1 commit
    • Tomasz Maczukin's avatar
      Remove legacy Runners support in /api/v4/jobs/request · 31e3f670b5be
      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.
      31e3f670b5be
  18. 02 Mar, 2017 6 commits
  19. 16 Feb, 2017 3 commits