-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins 1.546
We have upgrade to Subversion Plugin 2.0.
Since this upgrade, the plugin doesn't work anymore.
We get such message in the log:
Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:40 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:47 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated ! Feb 04, 2014 11:07:52 AM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator expectScmRepositoryInitiatedSCM Repository has not yet been initiated !
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
JENKINS-18124 Proposal : Modularizing scm-sync-config scm implementations
-
- Closed
-
-
-
- Closed
-
[JENKINS-21640] scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Stoil Valchkov
added a comment - Unfortunately we are with Subversion plugin 2.1 and would really like to use SCM plugin. Is there a workaround? It would be great if we can somehow fix it at least temporarily.
Thanks
Stoil Valchkov
added a comment - Unfortunately we are with Subversion plugin 2.1 and would really like to use SCM plugin. Is there a workaround? It would be great if we can somehow fix it at least temporarily.
Thanks 
Frédéric Camblor
added a comment - Downgrade to subversion plugin < 2.0
But I don't know if the downgrade will play well with your upgraded config.xml files, make tests before downgrading.
Frédéric Camblor
added a comment - Downgrade to subversion plugin < 2.0
But I don't know if the downgrade will play well with your upgraded config.xml files, make tests before downgrading. Stoil Valchkov
added a comment - That will require much efforts for reconfiguration of the existing jobs. For time being we'll try https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin. Our main goal is to have a way to view changes in configurations.
Stoil Valchkov
added a comment - That will require much efforts for reconfiguration of the existing jobs. For time being we'll try https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin . Our main goal is to have a way to view changes in configurations. 
Frédéric Camblor
added a comment - Yup, this plugin is a good alternative 
alex mattern
added a comment - I am having the same issue with Subversion Plugin 2.4 I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/*
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
Alan Birtles
added a comment - - edited I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/*
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job 
Roel Harbers
added a comment - So, with this blocker ticket being open for more than a year, I guess we can conclude that this is not going to work anytime soon?
What would be the consequences of using an ancient version of the Subversion plugin? (<2.0)
Roel Harbers
added a comment - So, with this blocker ticket being open for more than a year, I guess we can conclude that this is not going to work anytime soon?
What would be the consequences of using an ancient version of the Subversion plugin? (<2.0) 
Arun Thomas
added a comment - SCM Sync plugin is working for me.
Jenkins: 1.599
Sub-version plugin: 2.5
SCM Sync Configuration plugin: 0.0.8
Environment: Windows Server 2008
Could this have been resolved? Has anyone else tried the latest plugins?
Arun Thomas
added a comment - SCM Sync plugin is working for me.
Jenkins: 1.599
Sub-version plugin: 2.5
SCM Sync Configuration plugin: 0.0.8
Environment: Windows Server 2008
Could this have been resolved? Has anyone else tried the latest plugins? 
Dan Rough
added a comment - @Arun Thomas are deletes and modifications working for you? The last time I attempted to use this plugin I encountered a problem if I renamed items - the sync with Git would fail. Have you come across this?
Dan Rough
added a comment - @Arun Thomas are deletes and modifications working for you? The last time I attempted to use this plugin I encountered a problem if I renamed items - the sync with Git would fail. Have you come across this? 
Cameron
added a comment - @Dan Rough: We had the problem with renaming jobs too (with the older version of Jenkins). I guess it's a known bug that just never got fixed. We remove the SCM plugin's subversion URL and then put it back as a workaround to make the plugin happy again.
Cameron
added a comment - @Dan Rough: We had the problem with renaming jobs too (with the older version of Jenkins). I guess it's a known bug that just never got fixed. We remove the SCM plugin's subversion URL and then put it back as a workaround to make the plugin happy again. Arun Thomas
added a comment - @Dan Rough: Yes, I am able to rename without errors with the current plugins. I remember having issues when renaming jobs with the older versions.
Arun Thomas
added a comment - @Dan Rough: Yes, I am able to rename without errors with the current plugins. I remember having issues when renaming jobs with the older versions. Dan Rough
added a comment - @Cameron, @Arun Thanks! Alan Birtles
added a comment - all working for me as well with jeninks 1.607, svn 2.5 and scm 0.0.8 Alan Birtles
added a comment - and broken again in 1.613, svn 2.5 and scm 0.0.8 
Craig Rodrigues
added a comment - Fixed in 0.0.9 
kennabec walp
added a comment - Is this actually fixed? I still see the same issues with 0.0.9 and Subversion 2.5.5
kennabec walp
added a comment - Is this actually fixed? I still see the same issues with 0.0.9 and Subversion 2.5.5 
Arg ... as if it weren't already complicated enough
Seems like maintaining compatibility will be a pain.
Note that I linked this issue with
JENKINS-18124about scm modularization.