BR-51 Update ddf-jaxb to run on changes, instead of nightly #14
+0
−7
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
|
build now |
|
Internal build has been started. Your results will be available at completion. See build progress in legacy Jenkins UI or in Blue Ocean UI. |
|
Build success! See the job results in legacy Jenkins UI or in Blue Ocean UI. |
AdamBurstynski
approved these changes
Nov 21, 2019
shaundmorris
approved these changes
Dec 2, 2019
There was a problem hiding this comment.
@TonyMorrison just create a github issue here on this project, add it into the summary, and link the issue to the description of this PR to the issue. 👍
bdeining
approved these changes
Dec 2, 2019
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.
What does this PR do?
The job has been running nightly for months but there has been no changes to the code, so the change will just be to run it if there is a code change.
This will be done by removing the trigger from the Jenkinsfile
Issue
#15
Reviewers
@shaundmorris
@AdamBurstynski
@coyotesqrl
@bdeining