summaryrefslogtreecommitdiff
path: root/spec/lib
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2016-01-08 17:31:35 +0000
committerStan Hu <stanhu@gmail.com>2016-01-08 17:31:35 +0000
commit7403df6ca7bd31cd002d6fcf3bf4aa02dd4478eb (patch)
tree199fcaf1278a6e1b87f57cbd7cd43e172b382561 /spec/lib
parent8429f6f409eb8911d21095bc0fff3db2e53efd22 (diff)
parent69209612e1793fcebcdb784074056d7a02b0f6f7 (diff)
downloadgitlab-ce-7403df6ca7bd31cd002d6fcf3bf4aa02dd4478eb.tar.gz
Merge branch 'suppress-allow-failure-builds' into 'master'
Suppress e-mails on failed builds if allow_failure is set Every time I push to GitLab, I get > 2 emails saying a spec failed when I don't care about the benchmarks and others that have `allow_failure` set to `true`. @ayufan mentioned creating a summary e-mail to prevent getting one e-mail per build, but the latter might actually be desirable. For example, I do want to know if Rubocop errors fail right away. See merge request !2178
Diffstat (limited to 'spec/lib')
-rw-r--r--spec/lib/gitlab/build_data_builder_spec.rb1
1 files changed, 1 insertions, 0 deletions
diff --git a/spec/lib/gitlab/build_data_builder_spec.rb b/spec/lib/gitlab/build_data_builder_spec.rb
index 839b30f1ff4..38be9448794 100644
--- a/spec/lib/gitlab/build_data_builder_spec.rb
+++ b/spec/lib/gitlab/build_data_builder_spec.rb
@@ -14,6 +14,7 @@ describe 'Gitlab::BuildDataBuilder' do
it { expect(data[:tag]).to eq(build.tag) }
it { expect(data[:build_id]).to eq(build.id) }
it { expect(data[:build_status]).to eq(build.status) }
+ it { expect(data[:build_allow_failure]).to eq(false) }
it { expect(data[:project_id]).to eq(build.project.id) }
it { expect(data[:project_name]).to eq(build.project.name_with_namespace) }
end