-
Bug
-
Resolution: Fixed
-
Critical
-
SCM Sync Configuration Plugin 0.0.6.1
Jenkins Subversion Plug-in 1.43
svn version 1.6.11 (r934486)
git version 1.7.11.3
CentOS 5.8
To reproduce:
1. Install and configure scm-sync-configuration to use Subversion.
- In my case, I was using a file:///... repo
2. Rename a job (configure job, change Project name).
Expected result:
Job is moved in Subversion repository.
Actual result:
1. scm-sync-configuration.fail.log: "Error while checking in file to scm repository"
2. Nothing happens in Subversion repository.
3. Any changes after this are queued up but never checked in.
Workaround:
Use git rather than svn. When using git as a backend, the plugin behaves as expected. Or if you need svn, the workaround is to make sure to never rename jobs.
- depends on
-
JENKINS-18129 Using credentials-plugin to authenticate against SCMs & getting rid of maven-scm-api
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-15898] Subversion back-end cannot handle renaming of jobs
This issue seems to impact us whenever a job is deleted. Currently have plug in version 0.0.7.3.
Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
SEVERE: [deleteHierarchy] Problem during remove : SVN remove failed.
Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.SCMManipulator
FINE: Deleting SCM hierarchy [C:\Program Files\Jenkins\scm-sync-configuration\checkoutConfiguration\jobs\Update Qt on 1840-vpc-build1] from SCM ...
Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness
FINEST: Processing commit : Commit hudson.plugins.scm_sync_configuration.model.Commit@14c3977 :
Author : Adam Gregory
Comment : SPR 22718: Job [Update Qt] hierarchy renamed from [jobs/Update Qt on 1840-vpc-build1] to [jobs/Update Qt] by agregory
Changeset :
A config.xml
A jobs/Update Qt/
D jobs/Update Qt on 1840-vpc-build1/
clint axeda
added a comment - I am having the issue as well and we have been for a long time. The issue happens when renaming or deleting jobs. The real issue is that once this bug triggers all subsequent changes to the project do not get saved to the scm at all and that's a real problem.
JENKINS-15128 lists the workaround which is horribly inconvenient on a very large build server with jobs building all day long.
I would be willing to contribute to the project if need be.
clint axeda
added a comment - I am having the issue as well and we have been for a long time. The issue happens when renaming or deleting jobs. The real issue is that once this bug triggers all subsequent changes to the project do not get saved to the scm at all and that's a real problem.
JENKINS-15128 lists the workaround which is horribly inconvenient on a very large build server with jobs building all day long.
I would be willing to contribute to the project if need be. I experienced this issue recently when renaming a job (and subsequently deleting it). I fixed the commit errors by logging into our Windows Jenkins server and completing the following steps:
- Ensure that an svn client is installed (I used TortoiseSVN)
- Navigate to C:\Program Files (x86)\Jenkins\scm-sync-configuration\checkoutConfiguration
- Delete the old project folder
- Ensure that the config.xml for the master (in the checkoutConfiguration directory) is updated to use the new name
- Commit the changes (or let Scm Sync do it)
- If any errors or conflicts occur with the old project folder, resolve them
After this, Scm Sync was able to complete future commits. Until renaming is reactivated for the plugin, I'll be avoiding deleting or renaming projects.
Clinton Barr
added a comment - - edited I experienced this issue recently when renaming a job (and subsequently deleting it). I fixed the commit errors by logging into our Windows Jenkins server and completing the following steps:
Ensure that an svn client is installed (I used TortoiseSVN)
Navigate to C:\Program Files (x86)\Jenkins\scm-sync-configuration\checkoutConfiguration
Delete the old project folder
Ensure that the config.xml for the master (in the checkoutConfiguration directory) is updated to use the new name
Commit the changes (or let Scm Sync do it)
If any errors or conflicts occur with the old project folder, resolve them
After this, Scm Sync was able to complete future commits. Until renaming is reactivated for the plugin, I'll be avoiding deleting or renaming projects. 
Frédéric Camblor
added a comment - FYI, JENKINS-15128 was fixed in 0.0.8
Could someone test this version (once it will have poped in jenkins plugin repos) to see if scm-api update from 1.6 to 1.9.1 wouldn't fix the issue for svn ?
Frédéric Camblor
added a comment - FYI, JENKINS-15128 was fixed in 0.0.8
Could someone test this version (once it will have poped in jenkins plugin repos) to see if scm-api update from 1.6 to 1.9.1 wouldn't fix the issue for svn ? 
slav dok
added a comment - I've tested 0.0.8
Jenkins 1.565.3 (LTS)
Still the same issue. Everything works until the job is renamed. Once it is renamed... the whole things breaks and no other commits are going through.
[INFO] SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration
Oct 15, 2014 5:06:56 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue
SEVERE: Error while processing commit queue : Error while copying file hierarchy to SCM checkouted directory
[INFO] SVN remove working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs
Oct 15, 2014 5:07:18 PM org.tmatesoft.svn.core.internal.util.DefaultSVNDebugLogger log
INFO: CLI: executing statement: CREATE TABLE DELETE_LIST (local_relpath TEXT PRIMARY KEY NOT NULL);
[INFO] SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration
Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles
SEVERE: [checkinFiles] Problem during SCM commit : svn: E175002: Commit failed (details follow):
svn: E175002: DELETE /!svn/wrk/90eaa215-4901-0010-a0d4-0b2a729a5a4c/DEV/JENKINS_CONFIGS/jobs/MyJob failed
Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue
SEVERE: Error while processing commit queue : Error while checking in file to scm repository
slav dok
added a comment - I've tested 0.0.8
Jenkins 1.565.3 (LTS)
Still the same issue. Everything works until the job is renamed. Once it is renamed... the whole things breaks and no other commits are going through.
[INFO] SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration
Oct 15, 2014 5:06:56 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue
SEVERE: Error while processing commit queue : Error while copying file hierarchy to SCM checkouted directory
[INFO] SVN remove working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs
Oct 15, 2014 5:07:18 PM org.tmatesoft.svn.core.internal.util.DefaultSVNDebugLogger log
INFO: CLI: executing statement: CREATE TABLE DELETE_LIST (local_relpath TEXT PRIMARY KEY NOT NULL);
[INFO] SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration
Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles
SEVERE: [checkinFiles] Problem during SCM commit : svn: E175002: Commit failed (details follow):
svn: E175002: DELETE /!svn/wrk/90eaa215-4901-0010-a0d4-0b2a729a5a4c/DEV/JENKINS_CONFIGS/jobs/MyJob failed
Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue
SEVERE: Error while processing commit queue : Error while checking in file to scm repository 
Thomas Müller
added a comment - Is there any progress here?
As far as I can see this is still an open issue, i.e. updating to the latest released version won't help?
Thomas Müller
added a comment - Is there any progress here?
As far as I can see this is still an open issue, i.e. updating to the latest released version won't help? This issue has been around for a long time and really needs to be addressed as it is a major problem with this plugin.
The workaround suggested in this ticket is completely unacceptable. I don't have a choice as to which repository is to be used, and Subversion is a perfectly acceptable tool for the job (far superior to GIT from an SCM perspective, but I don't want to start a religious war here).
Brian Wilson
added a comment - - edited This issue has been around for a long time and really needs to be addressed as it is a major problem with this plugin.
The workaround suggested in this ticket is completely unacceptable. I don't have a choice as to which repository is to be used, and Subversion is a perfectly acceptable tool for the job (far superior to GIT from an SCM perspective, but I don't want to start a religious war here). 
Craig Rodrigues
added a comment - Fixed in 0.0.9 Brian Wilson
added a comment - Unfortunately the 0.0.9 revision of SCM Sync also introduces a serious bug. When you restart Jenkins, the web UI is just blank screen. Revision 0.0.9 is seriously flawed and should not be used.
Brian Wilson
added a comment - Unfortunately the 0.0.9 revision of SCM Sync also introduces a serious bug. When you restart Jenkins, the web UI is just blank screen. Revision 0.0.9 is seriously flawed and should not be used. 
(sorry, accidentally commented on the wrong issue)