[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall commented on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk I think that there are actually two bugs. I have now downgraded to 1.472 as you suggested. The behaviour I see is the same as that of the 1.475 release candidate that I was trying before (see my earlier comment for details). So I agree that the really serious bug does not seem to be present in that version. But I am still getting null pointer exceptions when Jenkins tries to load my old multi-configuration jobs, which I created in my old Jenkins system. I can live with this, because I haven't got many of those jobs, and I can re-create them manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall commented on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk I have tried this again with "Jenkins ver. 1.475-SNAPSHOT (rc-07/11/2012 15:57 GMT-kohsuke)" It is definitely better: I can now create multi-configuration jobs and restart Jenkins, and they do re-load. However, I can still provoke a NPE by copying old multi-configuration jobs from my old Jenkins machine (running Jenkins 1.441). They seem to be OK at the first reload from disk, but after restarting Jenkins again they no longer load, and the log shows a NPE. I have investigated the difference between the jobs. The top-level config.xml files differ slightly. The one created by the new Jenkins has some extra lines near the end of the file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall edited a comment on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk I have tried this again with "Jenkins ver. 1.475-SNAPSHOT (rc-07/11/2012 15:57 GMT-kohsuke)" It is definitely better: I can now create multi-configuration jobs and restart Jenkins, and they do re-load. However, I can still provoke a NPE by copying old multi-configuration jobs from my old Jenkins machine (running Jenkins 1.441). They seem to be OK at the first reload from disk, but after restarting Jenkins again they no longer load, and the log shows a NPE. I have investigated the difference between the jobs. The top-level config.xml files differ slightly. The one created by the new Jenkins has some extra lines near the end of the file. This is the new material: executionStrategy class="hudson.matrix.DefaultMatrixExecutionStrategyImpl" runSequentiallyfalse/runSequentially /executionStrategy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall assigned JENKINS-14474 to Sarah Woodall Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Change By: Sarah Woodall (18/Jul/12 11:08 AM) Assignee: SarahWoodall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall assigned JENKINS-14474 to Unassigned Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Change By: Sarah Woodall (18/Jul/12 11:08 AM) Assignee: SarahWoodall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14337) Multi-configuration job disappearing from list whether the file config.xml is edited.
Sarah Woodall commented on JENKINS-14337 Multi-configuration job disappearing from list whether the file config.xml is edited. Please see a new issue that I have just created: https://issues.jenkins-ci.org/browse/JENKINS-14474 I think you are seeing the same bug as I am! Have you tried just reloading from disk without editing config.xml at all? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall commented on JENKINS-13790 Subversion externals fail I am also seeing this problem. I have just installed the latest Jenkins (now 1.474) on a brand-new Windows machine. The plugin manager in Jenkins told me that the Subversion plugin was out of date (it was version 1.39), so I updated it to the latest one (1.42) before starting to set up my builds. These same builds had worked fine on a different Windows machine, which was running Jenkins 1.441 with version 1.34 of the Subversion plugin. When my builds checked their sources out of Subversion I got this message: AssertionError: appears to be using unpatched svnkit at jar:file:/Q:/jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class These builds are performed entirely on the (Windows) master, not on any slaves. Our repositories use svn externals, so I assume I am seeing the same problem that others have reported here. I am having trouble going back to version 1.39 of the Subversion plugin, because of the incompatibility in working copy layout between svn 1.6 and 1.7 (I have also installed TortoiseSVN and the command-line svn client, and I want to use Subversion 1.7 for everything on this new machine). I would really appreciate a fix for this bug so that I can use a version of the plugin that is compatible with svn 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall updated JENKINS-13790 Subversion externals fail Change By: Sarah Woodall (16/Jul/12 3:51 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall started work on JENKINS-13790 Subversion externals fail Change By: Sarah Woodall (16/Jul/12 3:51 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall edited a comment on JENKINS-13790 Subversion externals fail I am also seeing this problem. I have just installed the latest Jenkins (now 1.474) on a brand-new Windows 7 machine. The plugin manager in Jenkins told me that the Subversion plugin was out of date (it was version 1.39), so I updated it to the latest one (1.42) before starting to set up my builds. These same builds had worked fine on a different Windows 7 machine, which was running Jenkins 1.441 with version 1.34 of the Subversion plugin. When my builds checked their sources out of Subversion I got this message: AssertionError: appears to be using unpatched svnkit at jar:file:/Q:/jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class These builds are performed entirely on the (Windows) master, not on any slaves. Our repositories use svn externals, so I assume I am seeing the same problem that others have reported here. I am having trouble going back to version 1.39 of the Subversion plugin, because of the incompatibility in working copy layout between svn 1.6 and 1.7 (I have also installed TortoiseSVN and the command-line svn client, and I want to use Subversion 1.7 for everything on this new machine). I would really appreciate a fix for this bug so that I can use a version of the plugin that is compatible with svn 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
