Выбрать ветку (тег)
  1. 10.04.2019 1 коммит
    • Kamil Trzciński's avatar
      Process at most 4 pipelines during push
      · 2b9492a2
      Kamil Trzciński создал 
      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. 09.04.2019 1 коммит
    • Luke Duncalfe's avatar
      Use Gitlab::PushOptions for `ci.skip` push option
      · 1883e320
      Luke Duncalfe создал 
      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
  5. 26.03.2019 1 коммит
    • Bob Van Landuyt's avatar
      Allow multiple repositories per project
      · d36415b7
      Bob Van Landuyt создал 
      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
  7. 25.03.2019 2 коммита
  9. 31.12.2018 1 коммит
    • Jonathon Reinhart's avatar
      Add support for Git push options, specifically ci.skip
      · ba781484
      Jonathon Reinhart создал 
      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
  11. 25.10.2018 2 коммита
  13. 27.06.2018 1 коммит
  15. 18.04.2018 1 коммит
  17. 07.03.2018 1 коммит
  19. 05.12.2017 1 коммит
  21. 28.06.2017 1 коммит
  23. 06.06.2017 1 коммит
  25. 13.05.2017 1 коммит
  27. 05.05.2017 2 коммита
  29. 29.03.2017 1 коммит
  31. 03.03.2017 1 коммит
  33. 02.11.2016 1 коммит
  35. 21.10.2016 1 коммит
    • Yorick Peterse's avatar
      Re-organize queues to use for Sidekiq
      · 97731760
      Yorick Peterse создал 
      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 otherwis...
      97731760
  37. 05.08.2016 1 коммит
  39. 30.06.2016 1 коммит
  41. 19.04.2016 1 коммит
  43. 11.04.2016 1 коммит
  45. 17.03.2016 1 коммит
  47. 17.02.2016 1 коммит
  49. 15.02.2016 1 коммит
  51. 11.02.2016 1 коммит
  53. 10.08.2015 1 коммит
  55. 10.04.2015 1 коммит
  57. 15.03.2015 1 коммит
  59. 10.03.2015 1 коммит
  61. 02.09.2014 1 коммит
  63. 13.08.2014 1 коммит
  65. 06.03.2014 2 коммита
  67. 29.04.2013 1 коммит
  69. 03.04.2013 1 коммит
  71. 25.02.2013 1 коммит