-
Notifications
You must be signed in to change notification settings - Fork 144
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
report and validate concurrent changes #166
Conversation
Conflicts: samples/application-conf/README.md samples/application-conf/application.properties
with the upstream changes
upstream changes
upstream changes
reportUpstreamChanges
Conflicts: utilities/ImpactUtilities.groovy
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.
I have just some minor comments. I did not test the code.
REPORT.md
Outdated
reportConcurrentChangesGitBranchReferencePatterns=${mainBuildBranch},.*main.*,main,release,feature.* | ||
``` |
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.
The main branch should be captured by the .main. pattern? So to it is a sort of "dead" pattern?
# typically this is the branch into which changes of the topic branch are planned to be merged into. | ||
# | ||
# sample: | ||
# reportConcurrentChangesGitBranchReferencePatterns=${mainBuildBranch},.*main.*,main,release,feature.* |
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.
Same comment main should be captured be .main.
zAppBuild provides a set of reporting capabilities, which are part of the build framework itself to address some common demands of mainframe development teams.
Developers are particularly interested if:
This contribution contains: