-
Notifications
You must be signed in to change notification settings - Fork 124
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
#37 Based on pull request started by @zilmTT #38
base: master
Are you sure you want to change the base?
Conversation
If the deletion and adding path share some characters the contains() function succeed and removes the added path. It should be checked if they are equal. This fixes some rename issues we discovered in our environment.
Before deleting the job hierarchy it is needed to check for changes on the files, e.g config.xml. While deleting a job it gets updated, this blocks the git -rm command from deleting this hierarchy. Commits should always come with proper messages, git command fails if the commit message is empty. Which put scm-sync in an dirty state if there are commits which cannot be pushed.
As i encountered some copy issues, e.g was not able to copy blank build/ dir, i implemented a basic filter for the FileUtil.copy function. This matches on any XML-File and on includes specified on ManualIncludes list from scm-sync-configuration.
Conflicts: src/main/java/hudson/plugins/scm_sync_configuration/SCMManipulator.java src/main/java/hudson/plugins/scm_sync_configuration/ScmSyncConfigurationBusiness.java src/main/java/hudson/plugins/scm_sync_configuration/ScmSyncConfigurationPlugin.java
Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests. |
What about merging this? |
@rodrigc can you merge this? |
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.
This pull request is full of white space changes. It's very unlikely that it will be approved with all this unrelated changes.
Re-pushing previous merge from @zilmTT as a starting point, so the CI errors can be reviewed (the last CI job showing the errors has expired).