Avoid sync config files from scm working dir. #30
Conversation
This file contains hidden or 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
Avoiding possible recursive sync of "jobs" folder.
Change org.jenkins-ci.plugins:plugin version to 1.424.
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
|
I had this happen to me a few times already - very annoying - any progress on getting this in? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In the job strategy the regex is "**/jobs//config.xml". But when the scm-sync-plugin have already synced some jobs then there is config files under scm-sync-configuration/checkoutConfiguration/jobs//config.xml. Those files will be catch by this regex making some kind of recursive sync and increasing the number of sync files really quickly.
I do not know why it actually did not happen from the beginning, but in our case the "recursive issue" happens only after we add manual sync path to the plugin.