-
Notifications
You must be signed in to change notification settings - Fork 322
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
Commit / tag on failure #132
Conversation
Also shows names as well as IDs in the Build Data section Code by @djl197 I just merged it onto a more current master
It doesn't cover all use cases, job status can be also Unstable. Some hetero list with dropdown cases should resolve it more dynamic and modular instead hardcoded checkboxes. |
Yep - this would be good (something we've found we need too, where a unit test fails it'd still be nice to pull the container to figure out why). |
Yep. Selecting a threshold or a multi-select box to cover all cases is a much better idea. |
@@ -73,6 +81,7 @@ public boolean isApplicable(Class<? extends Job> jobType) { | |||
public DockerJobProperty newInstance(StaplerRequest sr, JSONObject formData) throws hudson.model.Descriptor.FormException { | |||
return new DockerJobProperty( | |||
(Boolean)formData.get("tagOnCompletion"), | |||
(Boolean)formData.get("tagOnFailure"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not use getBoolean method?
#181 related |
Closing due to inactivity. |
Also shows names as well as IDs in the Build Data section
Code by @djl197 I just merged it onto a more current master