-
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
-
JENKINS-21827 Error with SCM-syn-configuration
-
- Closed
-
-
JENKINS-22951 SCM Sync no longer working as of last few versions.
-
- Closed
-
-
JENKINS-24226 use credentials-plugin to define SCM credentials
-
- Closed
-
- is related to
-
JENKINS-18124 Proposal : Modularizing scm-sync-config scm implementations
-
- Closed
-
-
JENKINS-18129 Using credentials-plugin to authenticate against SCMs & getting rid of maven-scm-api
-
- Closed
-
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)