An error occurred fetching the project authors.
  1. 29 Apr, 2019 1 commit
  2. 10 Apr, 2019 1 commit
    • Kamil Trzciński's avatar
      Process at most 4 pipelines during push · 2b9492a2
      Kamil Trzciński authored
      This adds a limitation that we will try to create pipeline
      for at most 4 first changes (branches and tags).
      
      This does not affect processing of Pipelines for Merge Requests,
      as each updated MR will have associated pipeline created.
      2b9492a2
  3. 08 Apr, 2019 1 commit
    • Luke Duncalfe's avatar
      Use Gitlab::PushOptions for `ci.skip` push option · 1883e320
      Luke Duncalfe authored
      Previously the raw push option Array was sent to Pipeline::Chain::Skip.
      
      This commit updates this class (and the chain of classes that pass the
      push option parameters from the API internal `post_receive` endpoint to
      that class) to treat push options as a Hash of options parsed by
      GitLab::PushOptions.
      
      The GitLab::PushOptions class takes options like this:
      
          -o ci.skip -o merge_request.create -o merge_request.target=branch
      
      and turns them into a Hash like this:
      
          {
            ci: {
              skip: true
            },
            merge_request: {
              create: true,
              target: 'branch'
            }
          }
      
      This now how Pipeline::Chain::Skip is determining if the `ci.skip` push
      option was used.
      1883e320
  4. 26 Mar, 2019 1 commit
    • Bob Van Landuyt's avatar
      Allow multiple repositories per project · d36415b7
      Bob Van Landuyt authored
      This changes the repository type from a binary `wiki?` to a type. So
      we can have more than 2 repository types.
      
      Now everywhere we called `.wiki?` and expected a boolean, we check
      that type.
      d36415b7
  5. 25 Mar, 2019 2 commits
  6. 31 Dec, 2018 1 commit
    • Jonathon Reinhart's avatar
      Add support for Git push options, specifically ci.skip · ba781484
      Jonathon Reinhart authored
      gitlab-org/gitlab-shell!166 added support for collecting push options
      from the environment, and passing them along to the
      /internal/post_receive API endpoint.
      
      This change handles the new push_options JSON element in the payload,
      and passes them on through to the GitPushService and GitTagPushService
      services.
      
      Futhermore, it adds support for the first push option, ci.skip.  With
      this change, one can use 'git push -o ci.skip' to skip CI pipe
      execution. Note that the pipeline is still created, but in the "skipped"
      state, just like with the 'ci skip' commit message text.
      
      Implements #18667
      ba781484
  7. 25 Oct, 2018 2 commits
  8. 27 Jun, 2018 1 commit
  9. 18 Apr, 2018 1 commit
  10. 07 Mar, 2018 1 commit
  11. 05 Dec, 2017 1 commit
  12. 27 Jun, 2017 1 commit
  13. 05 Jun, 2017 1 commit
  14. 12 May, 2017 1 commit
  15. 05 May, 2017 2 commits
  16. 29 Mar, 2017 1 commit
  17. 03 Mar, 2017 1 commit
  18. 01 Nov, 2016 1 commit
  19. 21 Oct, 2016 1 commit
    • Yorick Peterse's avatar
      Re-organize queues to use for Sidekiq · 97731760
      Yorick Peterse authored
      Dumping too many jobs in the same queue (e.g. the "default" queue) is a
      dangerous setup. Jobs that take a long time to process can effectively
      block any other work from being performed given there are enough of
      these jobs.
      
      Furthermore it becomes harder to monitor the jobs as a single queue
      could contain jobs for different workers. In such a setup the only
      reliable way of getting counts per job is to iterate over all jobs in a
      queue, which is a rather time consuming process.
      
      By using separate queues for various workers we have better control over
      throughput, we can add weight to queues, and we can monitor queues
      better. Some workers still use the same queue whenever their work is
      related. For example, the various CI pipeline workers use the same
      "pipeline" queue.
      
      This commit includes a Rails migration that moves Sidekiq jobs from the
      old queues to the new ones. This migration also takes care of doing the
      inverse if ever needed. This does require downtime as otherwise new jobs
      could be scheduled in the old queues after this migration completes.
      
      This commit also includes an RSpec test that blacklists the use of the
      "default" queue and ensures cron workers use the "cronjob" queue.
      
      Fixes gitlab-org/gitlab-ce#23370
      97731760
  20. 05 Aug, 2016 1 commit
  21. 30 Jun, 2016 1 commit
  22. 19 Apr, 2016 1 commit
  23. 11 Apr, 2016 1 commit
  24. 17 Mar, 2016 1 commit
  25. 17 Feb, 2016 1 commit
  26. 15 Feb, 2016 1 commit
  27. 11 Feb, 2016 1 commit
  28. 10 Aug, 2015 1 commit
  29. 10 Apr, 2015 1 commit
  30. 15 Mar, 2015 1 commit
  31. 10 Mar, 2015 1 commit
  32. 02 Sep, 2014 1 commit
  33. 13 Aug, 2014 1 commit
  34. 06 Mar, 2014 1 commit
  35. 05 Mar, 2014 1 commit
  36. 29 Apr, 2013 1 commit
  37. 03 Apr, 2013 1 commit