39203f1adf
This change simplifies a Pipeline processing by introducing a special new status: created. This status is used for all builds that are created for a pipeline. We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped). This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled. This also allows us to visualise a full pipeline (with created builds). This also removes an after_touch used for updating a pipeline state parameters. Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
36 lines
957 B
Ruby
36 lines
957 B
Ruby
require 'spec_helper'
|
|
|
|
describe Ci::CreateTriggerRequestService, services: true do
|
|
let(:service) { described_class.new }
|
|
let(:project) { create(:project) }
|
|
let(:trigger) { create(:ci_trigger, project: project) }
|
|
|
|
before do
|
|
stub_ci_pipeline_to_return_yaml_file
|
|
end
|
|
|
|
describe '#execute' do
|
|
context 'valid params' do
|
|
subject { service.execute(project, trigger, 'master') }
|
|
|
|
it { expect(subject).to be_kind_of(Ci::TriggerRequest) }
|
|
it { expect(subject.builds.first).to be_kind_of(Ci::Build) }
|
|
end
|
|
|
|
context 'no commit for ref' do
|
|
subject { service.execute(project, trigger, 'other-branch') }
|
|
|
|
it { expect(subject).to be_nil }
|
|
end
|
|
|
|
context 'no builds created' do
|
|
subject { service.execute(project, trigger, 'master') }
|
|
|
|
before do
|
|
stub_ci_pipeline_yaml_file('script: { only: [develop], script: hello World }')
|
|
end
|
|
|
|
it { expect(subject).to be_nil }
|
|
end
|
|
end
|
|
end
|