Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32124

SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Windows 2012 R2, Linux RHEL5 and RHEL7, OSX 10.10, Jenkins 1.642.2, LTS, Subversion plugin 1.54 or 2.5.7
    • Similar Issues:

      Description

      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 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.

        Attachments

          Activity

          medianick Nick Jones created issue -
          medianick Nick Jones made changes -
          Field Original Value New Value
          Description 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:

          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.
          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 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.
          Hide
          muellert Thomas Müller added a comment -

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

          Show
          muellert Thomas Müller added a comment - This also bit me and I'd really like to install 0.0.9 to be able to rename jobs...
          Hide
          medianick Nick Jones added a comment -

          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.

          Show
          medianick Nick Jones added a comment - 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.
          Hide
          brianswilson Brian Wilson added a comment - - edited

          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.K.A. White Screen of Death, or WSoD). Before you 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).
          • 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.ScmSyncNoSCM"/>

          • 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.
          • Change the following lines:

          <credentials class="hashtable">
          <entry>
          <string><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. 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.

          Show
          brianswilson Brian Wilson added a comment - - edited 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.K.A. White Screen of Death, or WSoD). Before you 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). 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 No 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. Change the following lines: <credentials class="hashtable"> <entry> <string>< 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. 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.
          Hide
          medianick Nick Jones added a comment -

          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.

          Show
          medianick Nick Jones added a comment - 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 Nick Jones made changes -
          Environment Windows 2012 R2, Jenkins 1.625.3 LTS, Subversion plugin 1.54 Windows 2012 R2, Jenkins 1.642.2 LTS, Subversion plugin 1.54 or 2.5.7
          Hide
          annetheagile AnneTheAgile added a comment -

          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.

          Show
          annetheagile AnneTheAgile added a comment - 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.
          Hide
          alanbirtles Alan Birtles added a comment -

          Yes I am seeing the same issue on OSX 10.10

          Show
          alanbirtles Alan Birtles added a comment - Yes I am seeing the same issue on OSX 10.10
          Hide
          javacody Cody Fyler added a comment -

          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.

          Show
          javacody Cody Fyler added a comment - 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.
          Hide
          ssbarnea Sorin Sbarnea added a comment -

          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.

          Show
          ssbarnea Sorin Sbarnea added a comment - 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.
          Hide
          advorsky73 Alexander Dvorsky added a comment -

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

          Show
          advorsky73 Alexander Dvorsky added a comment - we are waiting for 0.0.9 to be fixed before installing the plugin.
          brianswilson Brian Wilson made changes -
          Environment Windows 2012 R2, Jenkins 1.642.2 LTS, Subversion plugin 1.54 or 2.5.7 Windows 2012 R2, Linux RHEL5 and RHEL7, Jenkins 1.642.2, LTS, Subversion plugin 1.54 or 2.5.7
          brianswilson Brian Wilson made changes -
          Environment Windows 2012 R2, Linux RHEL5 and RHEL7, Jenkins 1.642.2, LTS, Subversion plugin 1.54 or 2.5.7 Windows 2012 R2, Linux RHEL5 and RHEL7, OSX 10.10, Jenkins 1.642.2, LTS, Subversion plugin 1.54 or 2.5.7
          Hide
          brunopereira Bruno Pereira added a comment -

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

          Show
          brunopereira Bruno Pereira added a comment - I was trying the 0.0.9 version of the plugin when I it this issue. There are any news regarding this problem?
          Hide
          jorgziegler Jörg Ziegler added a comment -

          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).

          Show
          jorgziegler Jörg Ziegler added a comment - 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).
          Hide
          brunopereira Bruno Pereira added a comment -

          Thanks for sharing your "work around"

          Show
          brunopereira Bruno Pereira added a comment - Thanks for sharing your "work around"
          Hide
          advorsky73 Alexander Dvorsky added a comment -

          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???

          Show
          advorsky73 Alexander Dvorsky added a comment - 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???
          Hide
          fcamblor Frédéric Camblor added a comment -

          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

          Show
          fcamblor Frédéric Camblor added a comment - 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
          Hide
          hardwickj James Hardwick added a comment -

          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!

          Show
          hardwickj James Hardwick added a comment - 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!
          Hide
          fcamblor Frédéric Camblor added a comment -

          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)

          Show
          fcamblor Frédéric Camblor added a comment - 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)
          Hide
          hardwickj James Hardwick added a comment -

          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...

          Show
          hardwickj James Hardwick added a comment - 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...
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 167607 ] JNJira + In-Review [ 182806 ]
          Hide
          wilson_ds_net Brian Wilson added a comment - - edited

          fcamblor: You can only downgrade using the button if you can see the UI. Since this issue prevents the UI 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.

          Show
          wilson_ds_net Brian Wilson added a comment - - edited fcamblor: You can only downgrade using the button if you can see the UI. Since this issue prevents the UI 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.
          Hide
          fcamblor Frédéric Camblor added a comment -

          Pinging Craig Rodrigues: he's the one in charge of the plugin since release 0.0.9

          Show
          fcamblor Frédéric Camblor added a comment - Pinging Craig Rodrigues : he's the one in charge of the plugin since release 0.0.9
          fcamblor Frédéric Camblor made changes -
          Assignee Frédéric Camblor [ fcamblor ] Craig Rodrigues [ rodrigc ]
          Hide
          yaztromo Brad BARCLAY added a comment -

          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.

          Show
          yaztromo Brad BARCLAY added a comment - 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.
          Hide
          nutmix2 john little added a comment - - edited

          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?

          Show
          nutmix2 john little added a comment - - edited 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?
          Hide
          wilson_ds_net Brian Wilson added a comment - - edited

          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

          Show
          wilson_ds_net Brian Wilson added a comment - - edited 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
          Hide
          nutmix2 john little added a comment -

          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.

          Show
          nutmix2 john little added a comment - Thanks Brian. I found a solution in case anyone else has the problem: cd /var/lib/jenkins/plugins touch scm-sync-configuration.jpi.disabled Now I get the web UI, and can build the projects again.
          Hide
          palani Palanivel Somasundaram added a comment - - edited

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

          Show
          palani Palanivel Somasundaram added a comment - - edited @john little - I think that just disables the whole SCM-sync-configuration plugin functionality, it does not actually fix the problem!!!
          Hide
          fsteff Flemming Steffensen added a comment - - edited

          Issue confirmed to still exist on SCM Sync Configuration 0.0.10

          Windows 2012 R2, Jenkins 2.4.8, 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?

          Show
          fsteff Flemming Steffensen added a comment - - edited Issue confirmed to still exist on SCM Sync Configuration 0.0.10 Windows 2012 R2, Jenkins 2.4.8, 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 Craig Rodrigues made changes -
          Assignee Craig Rodrigues [ rodrigc ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            medianick Nick Jones
            Votes:
            18 Vote for this issue
            Watchers:
            30 Start watching this issue

              Dates

              Created:
              Updated: