Removed exception throw when calling isFingerprintConfigured #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was causing the promotion process to *always* fail when also running the Build Environment Plugin v1.6. The Build Environment Plugin will always check if a process has fingerprint enabled, and this would always throw an exception. The dummy implementation the fingerprint method should just return false.
|
👍 . A support of Fingerprints would be useful, but it's better than the original behavior |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
oleg-nenashev
added a commit
that referenced
this pull request
Nov 21, 2015
Removed exception throw when calling isFingerprintConfigured
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was causing the promotion process to always fail when also running
the Build Environment Plugin v1.6.
The Build Environment Plugin will always check if a process has fingerprint
enabled, and this would always throw an exception. The dummy implementation
the fingerprint method should just return false.