[JIRA] [scm-sync-configuration-plugin] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

49 views
Skip to first unread message

medianick@gmail.com (JIRA)

unread,
Dec 17, 2015, 9:08:09 AM12/17/15
to jenkinsc...@googlegroups.com
Nick Jones updated an issue
 
Jenkins / Bug JENKINS-32124
SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Change By: Nick Jones
After upgrading from version 0.0.8 to 0.0.9 of this plugin, the Jenkins UI fails to load upon restart. The "Jenkins" service is running  serving  but serves  no content to browsers. The error log shows the following stack trace:

Dec 17, 2015 7:59:54 AM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin scm-sync-configuration
java.io.IOException: Failed to initialize
at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441)
at hudson.PluginManager$2$1$1.run(PluginManager.java:371)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:905)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(Unknown Source)
at sun.reflect.UnsafeQualifiedObjectFieldAccessorImpl.get(Unknown Source)
at java.lang.reflect.Field.get(Unknown Source)
at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:59)
at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:66)
at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:72)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:67)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.initialInit(ScmSyncConfigurationPlugin.java:174)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.start(ScmSyncConfigurationPlugin.java:157)
at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449)
at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438)
... 9 more

Manually downgrading the scm-sync-configuration plugin to 0.0.8 and restarting solves the problem. I've done this upgrade/downgrade cycle twice to confirm that this is indeed the cause.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

medianick@gmail.com (JIRA)

unread,
Dec 17, 2015, 9:08:09 AM12/17/15
to jenkinsc...@googlegroups.com
Nick Jones created an issue
Issue Type: Bug Bug
Assignee: Frédéric Camblor
Components: scm-sync-configuration-plugin
Created: 17/Dec/15 2:07 PM
Environment: Windows 2012 R2, Jenkins 1.625.3 LTS, Subversion plugin 1.54
Priority: Blocker Blocker
Reporter: Nick Jones

After upgrading from version 0.0.8 to 0.0.9 of this plugin, the Jenkins UI fails to load upon restart. The "Jenkins" service is running serving no content to browsers. The error log shows the following stack trace:

thomas.mueller@tngtech.com (JIRA)

unread,
Jan 20, 2016, 9:08:01 AM1/20/16
to jenkinsc...@googlegroups.com
Thomas Müller commented on Bug JENKINS-32124
 
Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

This also bit me and I'd really like to install 0.0.9 to be able to rename jobs...

medianick@gmail.com (JIRA)

unread,
Jan 20, 2016, 11:12:02 AM1/20/16
to jenkinsc...@googlegroups.com

Absolutely! The job renaming is the main reason I want an updated version. Bouncing Jenkins (to clear up the SCM Sync "errors") every time someone renames a job is a bit tedious.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:14:04 PM1/21/16
to jenkinsc...@googlegroups.com

I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected. If you restart the Jenkins instance, the UI vanishes. If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files. The process I used is as follows (I used Linux, but this can be done on Windows as well):

  1. Exit the current Jenkins instance (e.g. http:.../Exit, kill -15, kill -9, whatever works).\
  2. Open a command shell on the Jenkins server.
  3. Become (i.e. change user to) the Jenkins process owner id.
  4. Open the scm-sync-configuration.xml in a text editor.
  5. Change the following lines
    <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
    <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>
    to

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:16:08 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

# Exit the current Jenkins instance (e.g.  http:.../Exit, kill -15, kill -9, whatever works).\
# Open a command shell on the Jenkins server.
# Become (i.e. change user to) the Jenkins process owner id.
# Open the scm-sync-configuration.xml in a text editor.
# Change the following lines

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>
to

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncNoSCM"/>

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:21:03 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

# Exit the current Jenkins instance (e.g.  http:.../Exit, kill -15, kill -9, whatever works).\
# Open a command shell on the Jenkins server.
# Become (i.e. change user to) the Jenkins process owner id.
# Open the scm-sync-configuration.xml  file  in a text editor.

# Change the following lines
:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>
to :

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncNoSCM"/>

# Open the hudson.scm.SubversionSCM.xml fine in a text editor.
# Change the following lines:

  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

to:

  <credentials class="hashtable"/>

# Restart your Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course).

This worked for me.  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:22:01 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):
# *  Exit the current Jenkins instance (e.g.  http:.../Exit, kill -15, kill -9, whatever works).\
 # *  Open a command shell on the Jenkins server.
 # *  Become (i.e. change user to) the Jenkins process owner id.
 # *  Open the scm-sync-configuration.xml file in a text editor.
 # *  Change the following lines:


  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

to:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncNoSCM"/>
# *  Open the hudson.scm.SubversionSCM.xml fine in a text editor.
 # *  Change the following lines:


  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

to:

  <credentials class="hashtable"/>

# *  Restart your Jenkins instance.


Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course).

This worked for me.  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:23:03 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the current Jenkins instance (e.g.  http:.../Exit, kill -15, kill -9, whatever works).\
* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
* Open the scm-sync-configuration.xml file in a text editor.
* Change the following lines:

{{   <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl> }}

to:

 {{   <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncNoSCM"/> }}
* Open the hudson.scm.SubversionSCM.xml fine in a text editor.
* Change the following lines:

{{   <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials> }}

to:

 {{   <credentials class="hashtable"/> }}

* Restart your Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course).

This worked for me.  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:24:02 PM1/21/16
to jenkinsc...@googlegroups.com

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:25:02 PM1/21/16
to jenkinsc...@googlegroups.com
* Restart  your  the  Jenkins instance.


Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course).

This worked for me.  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:43:04 PM1/21/16
to jenkinsc...@googlegroups.com
* Restart the Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course)  and could restart Jenkins with no further issues .

 To install the 0.0.8 SCM Sync plugin do the following process.

* Stop the Jenkins instance.
* Change directory to the Jenkins instance "plugins" subdirectory.
* Open the SYM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me  (Jenkins 1 . 645).   I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:44:02 PM1/21/16
to jenkinsc...@googlegroups.com
To install the 0.0.8 SCM Sync plugin  (or any other plugin for that matter)  do the following process.


* Stop the Jenkins instance.
* Change directory to the Jenkins instance "plugins" subdirectory.
* Open the SYM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:47:07 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the  current  currently running  Jenkins instance (e.g.  http:.../ Exit exit , kill -15, kill -9, whatever works).\

* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
*  Change directory to the Jenkins instance home directory (can't give you exact location because this is user installation dependent; but /data/jenkins or C:\jenkins is often used).
*  Open the scm-sync-configuration.xml file in a text editor.

* Change the following lines:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

    to:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncNoSCM"/>

* Open the hudson.scm.SubversionSCM.xml fine in a text editor.
* Change the following lines:

  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

    to:

  <credentials class="hashtable"/>

* Restart the Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course) and could restart Jenkins with no further issues.

To install the 0.0.8 SCM Sync plugin (or any other plugin for that matter) do the following process.

*  Stop  Exit  the  currently running  Jenkins instance   (e . g.  http:.../exit, kill -15, kill -9, whatever works).
* Change directory to the Jenkins instance  home  "plugins" subdirectory.

* Open the SYM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:49:04 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the currently running Jenkins instance (e.g.  http:.../exit, kill -15, kill -9, whatever works).\

* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
* Change directory to the Jenkins instance home directory (can't give you exact location because this is user installation dependent; but /data/jenkins or C:\jenkins is often used).
* Open the scm-sync-configuration.xml file in a text editor.
* Change the following lines:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

    to  just :

  <scm class="hudson.plugins.scm_sync_configuration.scms. ScmSyncNoSCM ScmSync{color:red}No{color}SCM "/>


* Open the hudson.scm.SubversionSCM.xml fine in a text editor.
* Change the following lines:

  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

    to  just :


  <credentials class="hashtable"/>

* Restart the Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course) and could restart Jenkins with no further issues.

To install the 0.0.8 SCM Sync plugin (or any other plugin for that matter) do the following process.

* Exit the currently running Jenkins instance  (e.g.  http:.../exit, kill -15, kill -9, whatever works).

* Change directory to the Jenkins instance home "plugins" subdirectory.
* Open the SYM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:49:05 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the currently running Jenkins instance (e.g.  http:.../exit, kill -15, kill -9, whatever works).\
* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
* Change directory to the Jenkins instance home directory (can't give you exact location because this is user installation dependent; but /data/jenkins or C:\jenkins is often used).
* Open the scm-sync-configuration.xml file in a text editor.
* Change the following lines:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

    to just:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSync{color:red}No{color}SCM"/>


* Open the hudson.scm.SubversionSCM.xml fine in a text editor.
* Change the following lines:

  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

    to just:

  <credentials class="hashtable" {color:red} / {color} >


* Restart the Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course) and could restart Jenkins with no further issues.

To install the 0.0.8 SCM Sync plugin (or any other plugin for that matter) do the following process.

* Exit the currently running Jenkins instance  (e.g.  http:.../exit, kill -15, kill -9, whatever works).
* Change directory to the Jenkins instance home "plugins" subdirectory.
* Open the SYM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:51:03 PM1/21/16
to jenkinsc...@googlegroups.com
* Open the  SYM  SCM  Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
*  Record the URL for the file version needed.   You can save the URL to download from in Windows by right clicking and selecting the "  Copy  Link Address..." menu option.
* Copy  the scm-sync-configuration.?pi file to scm-sync-configuration.bak

* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.
  You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 12:52:01 PM1/21/16
to jenkinsc...@googlegroups.com
* Change directory to the Jenkins instance home "plugins" subdirectory  (still as the Jenkins process owner id) .
* Open the SCM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).

* Record the URL for the file version needed.   You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved). This worked for me (Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 1:04:04 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the currently running Jenkins instance (e.g.  http:.../exit, kill -15, kill -9, whatever works).\
* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
* Change directory to the Jenkins instance home directory (can't give you exact location because this is user installation dependent; but /data/jenkins or C:\jenkins is often used).
*  Copy the scm-sync-configuration.xml file to scm-sync-configuration.bak (you will want this later).
*  Open the scm-sync-configuration.xml file in a text editor.

* Change the following lines:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

    to just:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSync{color:red}No{color}SCM"/>

*  Copy the hudson.scm.SubversionSCM.xml file to hudson.scm.SubversionSCM.bak (you will want this later also).
*  Open the hudson.scm.SubversionSCM.xml  fine  file  in a text editor.

* Change the following lines:

  <credentials class="hashtable">
    <entry>
      <string>&lt;https://svn.XXXX.com:443&gt; CollabNet Subversion Repository</string>
      <hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
        <userName>XXXXX</userName>
        <password>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=</password>
      </hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
    </entry>
  </credentials>

    to just:

  <credentials class="hashtable"{color:red}/{color}>

* Restart the Jenkins instance.

Once I did this, I could see my UI again (but didn't have the SCM Sync configured any more of course) and could restart Jenkins with no further issues.

To install the 0.0.8 SCM Sync plugin (or any other plugin for that matter) do the following process.

* Exit the currently running Jenkins instance  (e.g.  http:.../exit, kill -15, kill -9, whatever works).
* Change directory to the Jenkins instance home "plugins" subdirectory (still as the Jenkins process owner id).
* Open the SCM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Record the URL for the file version needed.   You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You  can restore your previous SCM configuration information by doing the following.

* Change directory to the Jenkins instance home directory (e.g. cd ..).
* Copy the scm-sync-configuration.bak file to scm-sync-configuration.xml.
* Copy the hudson.scm.SubversionSCM.bak file to hudson.scm.SubversionSCM.xml
* In the UI console, go to "Manage Jenkins and select the "Reload Configuration from Disk" option.
* Go the the "Manager Jenkins", "Configure System" screen and verify the SCM Sync configuration has been restored.
* Restart the Jenkins instance to verify the issue remains resolved.

You  should now see the previous version of the plugin is installed (don't update until this issue is resolved)  and still have the Jenkins SCM Sync plugin configured and working . .  This worked for me ( using Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Jan 21, 2016, 1:12:01 PM1/21/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well  in both Windows and Linux Jenkins instances .   This is definitely not a nice bug and can be difficult to trace since it only manifests on restart.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the UI vanishes.  If you configure the plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the UI is still present.

Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the currently running Jenkins instance (e.g.  http:.../exit, kill -15, kill -9, whatever works).\
* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id.
* Change directory to the Jenkins instance home directory (can't give you exact location because this is user installation dependent; but /data/jenkins or C:\jenkins is often used).
* Copy the scm-sync-configuration.xml file to scm-sync-configuration.bak (you will want this later).
* Open the scm-sync-configuration.xml file in a text editor.
* Change the following lines:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM"/>
  <scmRepositoryUrl>scm:svn:https://svn.autotrader.com/svn/jenkins_admin/branches/taxi49427</scmRepositoryUrl>

    to just:

  <scm class="hudson.plugins.scm_sync_configuration.scms.ScmSync{color:red}No{color}SCM"/>

* Copy the hudson.scm.SubversionSCM.xml file to hudson.scm.SubversionSCM.bak (you will want this later also).
* Open the hudson.scm.SubversionSCM.xml file in a text editor.
You should now see the previous version of the plugin is installed (don't update until this issue is resolved) and still have the Jenkins SCM Sync plugin configured and working.. This worked for me (using Jenkins 1.645).  I hope it works for others as well.

medianick@gmail.com (JIRA)

unread,
Mar 3, 2016, 11:55:04 AM3/3/16
to jenkinsc...@googlegroups.com

Out of curiosity, I just tested this again on Jenkins 1.642.2, also upgrading the Subversion plugin to 2.5.7, and after service restart I got the same blank UI again. Once I reverted to the previous versions of these two plugins (which I'd copied to an alternate location prior to upgrading) and restarted the service, the UI was back. So that's yet another confirmation that the 0.0.9 version of this plugin is the source of this bug.

medianick@gmail.com (JIRA)

unread,
Mar 3, 2016, 11:56:02 AM3/3/16
to jenkinsc...@googlegroups.com
Nick Jones updated an issue
 
Change By: Nick Jones
Environment: Windows 2012 R2, Jenkins 1. 625 642 . 3 2  LTS, Subversion plugin 1.54  or 2.5.7

annemoroney@alum.mit.edu (JIRA)

unread,
Mar 16, 2016, 2:40:01 PM3/16/16
to jenkinsc...@googlegroups.com
AnneTheAgile commented on Bug JENKINS-32124
 
Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

Does this also affect Mac? I assume not since if so, then every OS would be affected?

Also, is there any clue why this is occurring, so one could look at fixing it?

Thank you for all the great logs and remarks.

alan.birtles@eu.sony.com (JIRA)

unread,
Mar 17, 2016, 5:09:01 AM3/17/16
to jenkinsc...@googlegroups.com

Yes I am seeing the same issue on OSX 10.10

cody.a.fyler@wellsfargo.com (JIRA)

unread,
Mar 18, 2016, 11:34:02 AM3/18/16
to jenkinsc...@googlegroups.com

This bug has been opened for quite some time. And it is a major problem. I was also bit by it today. I think the 0.0.9 version should be removed.

sorin.sbarnea@gmail.com (JIRA)

unread,
Mar 18, 2016, 12:17:04 PM3/18/16
to jenkinsc...@googlegroups.com

Also it seems that the same version breaks Jenkins when you try to restart from the web interface (plugin updates). It will break starting to return empty HTTP responses which are downloaded as files by the browser!

If you do a `service jenkins restart` it will start correctly but that's clearly not good-enough.

advorsky@vasco.com (JIRA)

unread,
Mar 25, 2016, 8:31:02 AM3/25/16
to jenkinsc...@googlegroups.com

we are waiting for 0.0.9 to be fixed before installing the plugin.

briansw@bellsouth.net (JIRA)

unread,
Mar 29, 2016, 9:43:02 AM3/29/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
I got bit by this one as well in both Windows and Linux Jenkins instances.  This is definitely not a nice bug and can be difficult to trace since it only manifests on restart.   While it appears the Jenkins application is running and executing tasks, you can't see the web User Interface (UI).  I don't know if this is a problem with Tomcat based installations as we are using the default Jetty server included with Jenkins 1.65X versions.

Initially the plugin works as expected and the config.xml files are stored in our Subversion repository as expected.  If you restart the Jenkins instance, the  web  UI vanishes  (A .   If K.A. White Screen of Death, or WSoD).  Before  you  configure  restart  the  Jenkins instance, if you configured the  plugin to use a repository, save the changes, and change the plugin status from using the repository back to "None" you can restart the system and the  web  UI is still present.


Upon further testing and some file differencing (thank heavens for BeyondCompare) I was able to restore the UI by making manual changes to the hudson.scm.SubversionSCM.xml and scm-sync-configuration.xml files.  The process I used is as follows (I used Linux, but this can be done on Windows as well):

*  Exit the currently running Jenkins instance (e.g.   stop the service,   http:.../exit, kill -15, kill -9, whatever works).\

* Open a command shell on the Jenkins server.
* Become (i.e. change user to) the Jenkins process owner id  (on Windows systems you will need to login as the Jenkins process owner then open a command shell) .
* Exit the currently running Jenkins instance  (e.g.   stop the service,   http:.../exit, kill -15, kill -9, whatever works).

* Change directory to the Jenkins instance home "plugins" subdirectory (still as the Jenkins process owner id).
* Open the SCM Sync Archive (http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/).
* Record the URL for the file version needed.   You can save the URL to download from in Windows by right clicking and selecting the "Copy Link Address..." menu option.
* Copy the scm-sync-configuration.?pi file to scm-sync-configuration.bak
* Download the scm-sync-configuration.hpi file (e.g. wget http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.8/scm-sync-configuration.hpi) to the plugins subdirectory.
* Start the Jenkins instance.
* Verify the SCM Sync version shown is the one expected.
* Restart the Jenkins instance to verify the issue is resolved.

You can restore your previous SCM configuration information by doing the following.

* Change directory to the Jenkins instance home directory (e.g. cd ..).
* Copy the scm-sync-configuration.bak file to scm-sync-configuration.xml.
* Copy the hudson.scm.SubversionSCM.bak file to hudson.scm.SubversionSCM.xml
* In the UI console, go to "Manage Jenkins and select the "Reload Configuration from Disk" option.
* Go the the "Manager Jenkins", "Configure System" screen and verify the SCM Sync configuration has been restored.
* Restart the Jenkins instance to verify the issue remains resolved.

You should now see the previous version of the plugin is installed (don't update until this issue is resolved) and still have the Jenkins SCM Sync plugin configured and working.. This worked for me (using Jenkins 1.645).  I hope it works for others as well.

briansw@bellsouth.net (JIRA)

unread,
Mar 29, 2016, 9:45:03 AM3/29/16
to jenkinsc...@googlegroups.com
Brian Wilson updated an issue
 
Change By: Brian Wilson
Environment: Windows 2012 R2,  Linux RHEL5 and  RHEL7,  Jenkins 1.642.2 ,  LTS, Subversion plugin 1.54 or 2.5.7

briansw@bellsouth.net (JIRA)

unread,
Mar 29, 2016, 9:45:04 AM3/29/16
to jenkinsc...@googlegroups.com
Brian Wilson updated an issue
Change By: Brian Wilson
Environment: Windows 2012 R2, Linux RHEL5 and  RHEL7,  OSX 10.10,  Jenkins 1.642.2, LTS, Subversion plugin 1.54 or 2.5.7

brunor.pereira@gmail.com (JIRA)

unread,
Jun 9, 2016, 2:40:03 AM6/9/16
to jenkinsc...@googlegroups.com
Bruno Pereira commented on Bug JENKINS-32124
 
Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

I was trying the 0.0.9 version of the plugin when I it this issue. There are any news regarding this problem?

jorg.ziegler@fotonic.com (JIRA)

unread,
Jun 9, 2016, 2:52:02 AM6/9/16
to jenkinsc...@googlegroups.com

I have seen very little (read: no) reaction from the authors of the plugin for months now so I've given up and helped myself by creating a simple jenkins job that runs a shell script on master every hour, backing up everything to SVN if there are any changes. Works like a charm and has no problem dealing with job deletion/addition/renaming. Until we switch to 2.x with pipelines&scripts, now I know that the configuration is backed up and versioned.

You'll need rsync and the CLI svn client installed on master and jenkins needs the credentials-binding plugin (to get your svn user/pass into the shell script).

brunor.pereira@gmail.com (JIRA)

unread,
Jun 9, 2016, 4:58:02 AM6/9/16
to jenkinsc...@googlegroups.com

Thanks for sharing your "work around"

advorsky@vasco.com (JIRA)

unread,
Jun 23, 2016, 5:57:02 AM6/23/16
to jenkinsc...@googlegroups.com

Well this is blocking us a long time now and assignee had last activity on June 2nd...
Any chance to increase the speed of the fix???
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

fcamblor@gmail.com (JIRA)

unread,
Jun 23, 2016, 7:17:04 AM6/23/16
to jenkinsc...@googlegroups.com

The best chance you have is to take lead of the project and spend your spare time fixing others' issues.
Project is open source, if you want to help, you're welcome

jamesdh@gmail.com (JIRA)

unread,
Jun 28, 2016, 11:56:06 AM6/28/16
to jenkinsc...@googlegroups.com

Frédéric Camblor can we at least pull down the 0.0.9 version for the time being to help a lot of people avoid a major headache? We love the work you've done on this, and it's still useable via the previous release!

fcamblor@gmail.com (JIRA)

unread,
Jun 28, 2016, 12:16:02 PM6/28/16
to jenkinsc...@googlegroups.com

Not sure if this is the way to go, 0.0.9 is not buggy on every installations (on mine, for instance, no problems ... but I'm on an old jenkins LTS version)

Don't you have the "downgrade to X.X.X" button on the <JENKINS_URL>/pluginManager/installed screen ?

Anyway, if you want to manually pull down a previous version, you can download hpi file from here and install it through plugin center (you will need to uninstall the "official" scm-sync-config plugin before since plugins with same id cannot cohabit on the same jenkins instance)

jamesdh@gmail.com (JIRA)

unread,
Jun 28, 2016, 3:08:01 PM6/28/16
to jenkinsc...@googlegroups.com

Frédéric Camblor I believe you only get the "downgrade to X.X.X" button if you previously had an old version installed.

Thanks for the tip/link on installing the old version. That should suffice! I'll probably be installing this on a new 2+ version today or tomorrow and will report back how that goes...

wilson@ds.net (JIRA)

unread,
Aug 25, 2016, 8:11:11 AM8/25/16
to jenkinsc...@googlegroups.com

https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=fcamblor: You can only downgrade using the button if you can see the UI. Since this issue prevents the UI frojm displaying, you have to go through a long and tedious process to manually remove the plugin from the xml configuration files just to get control of your Jenkins instance back. I've confirmed this remains an issue for the Jenkins 2.X.X releases and is still an issue in the 0.0.10 release of the SCM Sync plugin. Our systems are using Java 1.8 and we will be switching to Java 1.9 in the near future.

While the 0.0.8 version is a great working plugin, the 0.0.9 release is clearly unreliable and should be deprecated or rescinded until a fix is in place. I've got this issue on multiple RHEL5, RHEL7, and Windows servers. I would really like to use the later features, but this issue is a show stopper.

wilson@ds.net (JIRA)

unread,
Aug 25, 2016, 8:11:16 AM8/25/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name= fcamblor: You can only downgrade using the button if you can see the UI.  Since this issue prevents the UI frojm displaying, you have to go through a long and tedious process to manually remove the plugin from the xml configuration files just to get control of your Jenkins instance back.  I've confirmed this remains an issue for the Jenkins 2.X.X releases and is still an issue in the 0.0.10 release of the SCM Sync plugin.  Our systems are using Java 1.8 and we will be switching to Java 1.9 in the near future.


While the 0.0.8 version is a great working plugin, the 0.0.9 release is clearly unreliable and should be deprecated or rescinded until a fix is in place.  I've got this issue on multiple RHEL5, RHEL7, and Windows servers.  I would really like to use the later features, but this issue is a show stopper.

wilson@ds.net (JIRA)

unread,
Aug 25, 2016, 8:12:02 AM8/25/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
fcamblor: You can only downgrade using the button if you can see the UI.  Since this issue prevents the UI frojm from displaying, you have to go through a long and tedious process to manually remove the plugin from the xml configuration files just to get control of your Jenkins instance back.  I've confirmed this remains an issue for the Jenkins 2.X.X releases and is still an issue in the 0.0.10 release of the SCM Sync plugin.  Our systems are using Java 1.8 and we will be switching to Java 1.9 in the near future.


While the 0.0.8 version is a great working plugin, the 0.0.9 release is clearly unreliable and should be deprecated or rescinded until a fix is in place.  I've got this issue on multiple RHEL5, RHEL7, and Windows servers.  I would really like to use the later features, but this issue is a show stopper.

fcamblor@gmail.com (JIRA)

unread,
Aug 25, 2016, 9:05:04 AM8/25/16
to jenkinsc...@googlegroups.com
Frédéric Camblor assigned an issue to Craig Rodrigues
 

Pinging Craig Rodrigues: he's the one in charge of the plugin since release 0.0.9
Change By: Frédéric Camblor
Assignee: Frédéric Camblor Craig Rodrigues

brad.barclay@infor.com (JIRA)

unread,
Dec 15, 2016, 5:19:01 PM12/15/16
to jenkinsc...@googlegroups.com
Brad BARCLAY commented on Bug JENKINS-32124
 
Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

Just hit upon this, running dcm-sync plugin 0.0.10. We're running the Jenkins Docker container on CentOS 7. Brian Wilson's "fix" to disable the plug-in and downgrade to 0.0.8 manually worked for us, however a proper fix to this issue would be greatly appreciated.

john.v.little@gmail.com (JIRA)

unread,
Feb 6, 2017, 12:20:04 PM2/6/17
to jenkinsc...@googlegroups.com

I just upgraded to 0.0.9 and now jenkins UI is giving blank pages also. In the logs it says

INFO: Jenkins is fully up and running

But it is not.

Earlier in the log file is one error:

Feb 06, 2017 6:08:26 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.9 (scm-sync-configuration)
java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521)

Please, could someone tell us how to manually downgrade the scm-sync-configuration plugin to 0.0.8?

john.v.little@gmail.com (JIRA)

unread,
Feb 6, 2017, 12:20:09 PM2/6/17
to jenkinsc...@googlegroups.com
john little edited a comment on Bug JENKINS-32124
I just upgraded to 0.0.9 and now jenkins UI is giving blank pages also.  In the logs it says

INFO: Jenkins is fully up and running

But it is not.

Earlier in the log file is one error:

Feb 06, 2017 6:08:26 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.9 (scm-sync-configuration)
java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521)
* Please, could someone tell us how to manually downgrade the scm-sync-configuration plugin to 0.0.8? *

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:25:02 PM2/6/17
to jenkinsc...@googlegroups.com

Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice go to the scm-sync web page.
find the archive link near top left hand side of the page.
download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
install the plugin file in the plugin subdirectory.
restart jenkins.

If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant and devastatingly handsome Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.

Hope this helps

Brian

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:26:04 PM2/6/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice go to the scm-sync web page.
find the archive link near top left hand side of the page.
download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
install the plugin file in the plugin subdirectory.
restart jenkins.


If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments.  Near the bottom, that brilliant and , devastatingly handsome , and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.

Hope this helps

Brian

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:27:02 PM2/6/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
You are experiencing the dreaded "White Screen of Death" (WSoD).  Some plugins will do this to you, some won't.

To answer your question, the simple way is:
Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice go to the scm-sync web page.
find the archive link near top left hand side of the page.
download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
install the plugin file in the plugin subdirectory.
restart jenkins.


If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments.  Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.

Hope this helps

Brian

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:29:04 PM2/6/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
You are experiencing the dreaded "White Screen of Death" (WSoD).  Some plugins will do this to you, some most won't.


To answer your question, the simple way is:
Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice go to the scm-sync web page.
find the archive link near top left hand side of the page.
download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
install the plugin file in the plugin subdirectory.
restart jenkins.


If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments.  Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.

Hope this helps

Brian

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:30:02 PM2/6/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
You are experiencing the dreaded "White Screen of Death" (WSoD).  Some plugins will do this to you, most won't.


To answer your question, the simple way is:
Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice , go to the scm-sync web page (link provided later in this messsage) .
 find Find the archive link near top left hand side of the page.
 download Download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
 install Install the plugin file in the plugin subdirectory.
 restart Restart jenkins.



If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments.  Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.

Hope this helps

Brian

wilson@ds.net (JIRA)

unread,
Feb 6, 2017, 2:31:01 PM2/6/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-32124
You are experiencing the dreaded "White Screen of Death" (WSoD).  Some plugins will do this to you, most won't.

To answer your question, the simple way is:
Go to the https://<server:port>/pluginManager/.
Find the scm-sync plugin.
Select the button to downgrade.

If you don't have that choice, go to the scm-sync web page (link provided later in this messsage).

Find the archive link near top left hand side of the page.
Download the 0.0.8 version of the plugin.
Stop the Jenkins instance.
Install the plugin file in the plugin subdirectory.
Restart jenkins.


If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments.  Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some very detailed instructions that should let you get back to what you need.

Hope this helps

Brian

john.v.little@gmail.com (JIRA)

unread,
Feb 6, 2017, 3:41:02 PM2/6/17
to jenkinsc...@googlegroups.com

Thanks Brian. I found a solution in case anyone else has the problem:

  1. cd /var/lib/jenkins/plugins
  2. touch scm-sync-configuration.jpi.disabled

Now I get the web UI, and can build the projects again.

perapalani@gmail.com (JIRA)

unread,
Feb 7, 2017, 9:35:02 AM2/7/17
to jenkinsc...@googlegroups.com

@john little - I think that just disables the whole SCM functionality, it does not actually fix the problem!!!

perapalani@gmail.com (JIRA)

unread,
Feb 7, 2017, 9:35:04 AM2/7/17
to jenkinsc...@googlegroups.com
@john little - I think that just disables the whole SCM -sync-configuration plugin functionality, it does not actually fix the problem!!!

fsteff@gmail.com (JIRA)

unread,
Mar 2, 2017, 9:54:02 AM3/2/17
to jenkinsc...@googlegroups.com

Issue confirmed to still exist on SCM Sync Configuration 0.0.10, installed on Windows server 2012.

Any progress or even ETA on a fix?

Any hints to how we (the community) can assist debugging this issue?

fsteff@gmail.com (JIRA)

unread,
Mar 2, 2017, 9:58:08 AM3/2/17
to jenkinsc...@googlegroups.com
Flemming Steffensen edited a comment on Bug JENKINS-32124
Issue confirmed to still exist on SCM Sync Configuration 0.0.10 , installed on

Windows server 2012 R2, Jenkins 2 . 4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8

Any progress or even ETA on a fix?

Any hints to how we (the community) can assist debugging this issue?

fsteff@gmail.com (JIRA)

unread,
Mar 2, 2017, 9:58:10 AM3/2/17
to jenkinsc...@googlegroups.com
Flemming Steffensen edited a comment on Bug JENKINS-32124
Issue confirmed to still exist on SCM Sync Configuration 0.0.10

Windows 2012 R2, Jenkins 2.4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8


Any progress or even ETA on a fix?

Any hints to how we (the community) can assist debugging this issue?

rodrigc@FreeBSD.org (JIRA)

unread,
Aug 28, 2018, 4:42:11 AM8/28/18
to jenkinsc...@googlegroups.com
Craig Rodrigues assigned an issue to Unassigned
 
Change By: Craig Rodrigues
Assignee: Craig Rodrigues
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages