gitlab-org--gitlab-foss/app/services/ci
Luke Duncalfe 1883e320ea Use Gitlab::PushOptions for `ci.skip` push option
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.
2019-04-09 10:03:26 +12:00
..
archive_trace_service.rb
compare_reports_base_service.rb
compare_test_reports_service.rb
create_pipeline_schedule_service.rb
create_pipeline_service.rb Use Gitlab::PushOptions for `ci.skip` push option 2019-04-09 10:03:26 +12:00
destroy_expired_job_artifacts_service.rb
destroy_pipeline_service.rb Clear pipeline status cache after destruction of pipeline 2019-03-26 01:04:06 -05:00
ensure_stage_service.rb
extract_sections_from_build_trace_service.rb
pipeline_trigger_service.rb Merge branch 'fix-misspellings-app-comments' into 'master' 2019-02-26 12:25:01 +01:00
play_build_service.rb
prepare_build_service.rb Create framework for build prerequisites 2019-03-20 12:04:40 +11:00
process_build_service.rb
process_pipeline_service.rb
register_job_service.rb
retry_build_service.rb
retry_pipeline_service.rb
run_scheduled_build_service.rb
stop_environments_service.rb
update_build_queue_service.rb
update_runner_service.rb