|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I'm having this problem too. Not all the time, though. Lets say 90% of the commits work fine, but for 10% the previous version is commited. However, in the SVN history (which I read in Eclipse) the commit comment is always recorded.
I can not reproduce this error. Sometimes it happens, sometimes it doesn't.
Sometimes I can see a commit comment "configuration updated by SYSTEM" in the SVN history when this happens.
Right now I have 18 jobs, with one config file out of sync:
.jenkins\jobs\myjob\config.xml 2013-05-15 08:43 is correct with my latest configurations saved.
.jenkins\scm-sync-configuration\checkoutConfiguration\jobs\myjob\config.xml 2012-05-15 08:44 is the previous version.
Please note the timestamps of the files
In SVN history I can read
862 2013-05-15 08:43 configuration updated with following comment: <mycomment>
863 2012-05-15 08:44 configuration updated by SYSTEM
Looks like I've successfully changed and commited the file, immediately followed by a commit performed by SYSTEM that reverts to previous version.
I'm running Jenkins 1.494
Installed plugins:
Jenkins Mailer Plugin 1.4
External Monitor Job type Plugin 1.1
LDAP Plugin 1.1
pam-auth 1.0
javadoc 1.0
Maven Integration plugin 1.494
Environment Injector Plugin 1.74
ant 1.1
Jenkins Subversion Plug-in 1.39
Jenkins CVS Plug-in 1.6
HTML Publisher Plugin 1.2
SCM Sync configuration plugin 0.0.6.1
Jenkins SSH Slaves plugin 0.22
Jenkins Translation Assistance plugin 1.8