Do not raise error when checking pipeline reference

Return from the `Ci::Pipeline#ref_exists?` in case when there is no
repository present.

This also fixes pipeline page feature specs by changing pipeline
reference instead of stubbing `ref_exist?` method.
This commit is contained in:
Grzegorz Bizon 2018-10-22 13:33:28 +02:00
parent 5f412e3a87
commit 680afb3d77
3 changed files with 34 additions and 17 deletions

View file

@ -270,6 +270,8 @@ module Ci
def ref_exists? def ref_exists?
project.repository.ref_exists?(git_ref) project.repository.ref_exists?(git_ref)
rescue Gitlab::Git::Repository::NoRepository
false
end end
## ##

View file

@ -241,9 +241,12 @@ describe 'Pipeline', :js do
end end
end end
context 'with deleted branch' do context 'when pipeline ref does not exist in repository anymore' do
before do let(:pipeline) do
allow(pipeline).to receive(:ref_exists?).and_return(false) create(:ci_empty_pipeline, project: project,
ref: 'non-existent',
sha: project.commit.id,
user: user)
end end
it 'does not render link to the pipeline ref' do it 'does not render link to the pipeline ref' do

View file

@ -780,6 +780,7 @@ describe Ci::Pipeline, :mailer do
end end
describe 'ref_exists?' do describe 'ref_exists?' do
context 'when repository exists' do
using RSpec::Parameterized::TableSyntax using RSpec::Parameterized::TableSyntax
let(:project) { create(:project, :repository) } let(:project) { create(:project, :repository) }
@ -802,6 +803,17 @@ describe Ci::Pipeline, :mailer do
end end
end end
context 'when repository does not exist' do
let(:pipeline) do
create(:ci_empty_pipeline, project: project, ref: 'master')
end
it 'always returns false' do
expect(pipeline.ref_exists?).to eq false
end
end
end
context 'with non-empty project' do context 'with non-empty project' do
let(:project) { create(:project, :repository) } let(:project) { create(:project, :repository) }