-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
centos
The jenkins scm sync plugin has been rendered quite useless for us since about 4 months because it creates loads of commits that are not related to configuration changes.
They commits look like this: "Job [*jobname*] configuration updated by SYSTEM"
The culprit is one of the default includes (Let me quote from the configuration page):
Following includes are brought "out of the box" by scm-sync-configuration default includes :
config.xml
hudson*.xml
scm-sync-configuration.xml
jobs/*/config.xml
---------
This include: jobs/*/config.xml monitors all config.xml files in our project for changes and commits them to svn.
Obviously this is not very helpful and can be considered pretty intrusive.
It would be nice if this entry could be removed from the default includes or ignored easily.
The affected config file starts like this:
<?xml version='1.0' encoding='UTF-8'?>
<maven2-module-set plugin="maven-plugin@1.498">
<keepDependencies>false</keepDependencies>
...
It contains lots of data of the maven pom(s) of the source that is built by the job. To save these changes in the poms in svn is beside the scope of the scm plugin. That is what we have version control for.
I did not find a way to override this predefined include. But maybe there is a way or maybe it should be removed.
- is related to
-
JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended?
- Closed