Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding generic build failed reason #13590

Merged
merged 1 commit into from
Mar 31, 2017
Merged

Adding generic build failed reason #13590

merged 1 commit into from
Mar 31, 2017

Conversation

coreydaley
Copy link
Member

@coreydaley coreydaley commented Mar 30, 2017

Adding a generic build failed reason to display to display
for build failures that do not have a more specific reason

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1436391

@coreydaley
Copy link
Member Author

[test]

@coreydaley
Copy link
Member Author

@openshift/devex ptal

Copy link
Contributor

@bparees bparees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd also like to see a test that fails w/ this reason if possible... i know that may be difficult so let's discuss if there's not an obvious failure path you can force the build down, but at least give it some thought.

@@ -343,6 +343,10 @@ func (bc *BuildPodController) HandlePod(pod *kapi.Pod) error {

case kapi.PodFailed:
nextStatus = buildapi.BuildPhaseFailed
if build.Status.Reason == "" {
build.Status.Reason = buildapi.StatusReasonGenericBuildFailed
build.Status.Message = "Generic Build failure - check logs for details."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make the message a constant too...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, looking at a potential test case

@coreydaley
Copy link
Member Author

[testextended][extended:core(builds)]

Adding a generic build failed reason to display to display
for build failures that do not have a more specific reason
@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 2baacf1

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test Running (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/521/) (Base Commit: 611176d)

@openshift-bot
Copy link
Contributor

Evaluated for origin testextended up to 2baacf1

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended/112/) (Base Commit: 611176d) (Extended Tests: core(builds))

@coreydaley
Copy link
Member Author

@bparees ptal, all tests are passing

@bparees
Copy link
Contributor

bparees commented Mar 31, 2017

[merge]

@bparees bparees self-assigned this Mar 31, 2017
@bparees
Copy link
Contributor

bparees commented Mar 31, 2017

flake #13594
[merge]

@bparees
Copy link
Contributor

bparees commented Mar 31, 2017 via email

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 2baacf1

@openshift-bot
Copy link
Contributor

openshift-bot commented Mar 31, 2017

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/230/) (Base Commit: a62d19f) (Image: devenv-rhel7_6109)

@openshift-bot openshift-bot merged commit b085941 into openshift:master Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants