[JIRA] (JENKINS-15730) Persisting too much
Christian Wolfgang created JENKINS-15730 Persisting too much Issue Type: Bug Assignee: Christian Wolfgang Components: logging Created: 06/Nov/12 8:02 AM Description: Accidentally persisting too much, causes enormous config.xml's Project: Jenkins Priority: Critical Reporter: Christian Wolfgang 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Erik Lovlie commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException Same here. Stack trace is nearly the same. 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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich
commented on JENKINS-15701
Integrate branch gives No changes to be integrated
After looking around in the code I think I found the place where it goes wrong:
final SVNException eureka = new SVNException(null);
try {
cm.getLogClient().doLog(new File[]{mr},mergeRev,SVNRevision.create(lastIntegrationSourceRevision),mergeRev,true,false,-1,new ISVNLogEntryHandler() {
public void handleLogEntry(SVNLogEntry e) throws SVNException {
if (e.getMessage().startsWith(RebaseAction.COMMIT_MESSAGE_PREFIX)
|| e.getMessage().startsWith(IntegrateAction.COMMIT_MESSAGE_PREFIX))
return; // merge commits
throw eureka;
}
});
// didn't find anything interesting. all the changes are our merges
logger.println("No changes to be integrated. Skipping integration.");
return new IntegrationResult(0,mergeRev);
} catch (SVNException e) {
if (e!=eureka)
throw e; // some other problems
// found some changes, keep on integrating
}
It seems like eureka is handled gracefully in the parsing process and so the catch block is never reached.
I'm not 100 percent sure, though, because debugging this part in netbeans is quite tricky Half of the time breakpoints are ignored in the inner classes.
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-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Andreas Zschorn updated JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Change By: Andreas Zschorn (06/Nov/12 8:22 AM) Priority: Critical Blocker 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-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Régis Desgroppes updated JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) Faced the same issue with Mercurial: Nov 5, 2012 10:31:42 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@60f38b42[reference_client_devel.centos5-x86_64.build] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Change By: Régis Desgroppes (06/Nov/12 8:28 AM) Summary: FailedtorecordSCMpolling(again)whilepollingfor Clearcase SCMchanges (Clearcase,Mercurial...) Priority: Major Blocker 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-15731) audit log: provide information who created/deleted a Jenkins job
Michael Prokop created JENKINS-15731 audit log: provide information who created/deleted a Jenkins job Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: audit-trail Created: 06/Nov/12 8:26 AM Description: Hi, currently the audit trail log provides information that a job was created/deleted by a user: Nov 6, 2012 9:21:52 AM hudson.plugins.audit_trail.AuditTrailFilter CONFIG: /view/All/createItem by mika Nov 6, 2012 9:21:27 AM hudson.plugins.audit_trail.AuditTrailFilter CONFIG: /job/createjob/doDelete by mika It would be nice if the audit trail log would contain the information which job was created/deleted. Thanks for the audit trail plugin! regards, Michael Project: Jenkins Priority: Major Reporter: Michael Prokop 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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich
edited a comment on JENKINS-15701
Integrate branch gives No changes to be integrated
After looking around in the code I think I found the place where it goes wrong:
FeatureBranchProperty.java
final SVNException eureka = new SVNException(null);
try {
cm.getLogClient().doLog(new File[]{mr},mergeRev,SVNRevision.create(lastIntegrationSourceRevision),mergeRev,true,false,-1,new ISVNLogEntryHandler() {
public void handleLogEntry(SVNLogEntry e) throws SVNException {
if (e.getMessage().startsWith(RebaseAction.COMMIT_MESSAGE_PREFIX)
|| e.getMessage().startsWith(IntegrateAction.COMMIT_MESSAGE_PREFIX))
return; // merge commits
throw eureka;
}
});
// didn't find anything interesting. all the changes are our merges
logger.println("No changes to be integrated. Skipping integration.");
return new IntegrationResult(0,mergeRev);
} catch (SVNException e) {
if (e!=eureka)
throw e; // some other problems
// found some changes, keep on integrating
}
It seems like eureka is handled gracefully in the parsing process and so the catch block is never reached.
I'm not 100 percent sure, though, because debugging this part in netbeans is quite tricky Half of the time breakpoints are ignored in the inner classes.
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-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Régis Desgroppes edited a comment on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) I faced the same issue yesterday after installing Jenkins 1.489. We're using Mercurial as SCM, so I guess the ticket affects all SCM plugins. Nov 5, 2012 10:31:42 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@60f38b42[reference_client_devel.centos5-x86_64.build] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Temporarily solved by reinstalling Jenkins 1.488. 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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich
edited a comment on JENKINS-15701
Integrate branch gives No changes to be integrated
After looking around in the code I think I found the place where it goes wrong (FeatureBranchProperty.java line 273):
FeatureBranchProperty.java
final SVNException eureka = new SVNException(null);
try {
cm.getLogClient().doLog(new File[]{mr},mergeRev,SVNRevision.create(lastIntegrationSourceRevision),mergeRev,true,false,-1,new ISVNLogEntryHandler() {
public void handleLogEntry(SVNLogEntry e) throws SVNException {
if (e.getMessage().startsWith(RebaseAction.COMMIT_MESSAGE_PREFIX)
|| e.getMessage().startsWith(IntegrateAction.COMMIT_MESSAGE_PREFIX))
return; // merge commits
throw eureka;
}
});
// didn't find anything interesting. all the changes are our merges
logger.println("No changes to be integrated. Skipping integration.");
return new IntegrationResult(0,mergeRev);
} catch (SVNException e) {
if (e!=eureka)
throw e; // some other problems
// found some changes, keep on integrating
}
It seems like eureka is handled gracefully in the parsing process and so the catch block is never reached.
I'm not 100 percent sure, though, because debugging this part in netbeans is quite tricky Half of the time breakpoints are ignored in the inner classes.
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-15732) Duplicated / multiple Jenkins CLI entries under Manage Jenkins
Michael Prokop created JENKINS-15732 Duplicated / multiple Jenkins CLI entries under Manage Jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 06/Nov/12 8:41 AM Description: Jenkins v1.489 has a bug where several entries under "Manage Jenkins" are called "Jenkins CLI": http://michael-prokop.at/screeni/gkrellShoot_12-11-06_092744.png The links themselves are OK though (linking to /log, /cli,...). I can not reproduce this issue with v1.488, as soon as upgrading the same system to 1.489 the bug reappears again. Project: Jenkins Priority: Major Reporter: Michael Prokop 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-15662) Cannot add post-build action for JaCoCo
Carsten Pfeiffer commented on JENKINS-15662 Cannot add post-build action for JaCoCo FWIW, when testing locally with mvn hpi:run, I tried once with the currently set jenkins target version 1.424.6 and another time with version 1488. It worked with both. 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
David Pärsson commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I have seen this issue (or a very similar one) when trying to generate Performance reports for huge JMeter reports. Jenkins v1.471 and Performance plugin v1.8. 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
David Pärsson edited a comment on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I think I have seen this issue (or a very similar one) when trying to generate Performance reports for huge JMeter reports. Jenkins v1.471 and Performance plugin v1.8. 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-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
joni r commented on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization I came across same issue while setting up Project-based Matrix Authorization Strategy -scheme. As a workaround I set job-read permission to all authenticated users at Jenkins level. 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-15733) Mercurial plugin crashes when polling repository
Karl Werf created JENKINS-15733 Mercurial plugin crashes when polling repository Issue Type: Bug Assignee: Jesse Glick Components: mercurial Created: 06/Nov/12 9:18 AM Description: Started on 2012-nov-06 10:06:07 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@114d662everything_but_bundle java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Project: Jenkins Labels: plugin Priority: Major Reporter: Karl Werf 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-15733) Mercurial plugin crashes when polling repository
Karl Werf updated JENKINS-15733 Mercurial plugin crashes when polling repository Change By: Karl Werf (06/Nov/12 9:20 AM) Description: IupgradedJenkinsandtheMercurialSCMpluginyesterdaytoversion1.41andnowitcrasheswhentryingtopollourrepository. Startedon2012-nov-0610:06:07ERROR:FailedtorecordSCMpollingforhudson.model.FreeStyleProject@114d662[everything_but_bundle]java.lang.ArrayIndexOutOfBoundsException:1 athudson.Launcher$2.launch(Launcher.java:712) athudson.Launcher$ProcStarter.start(Launcher.java:346) athudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) athudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) athudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) athudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) athudson.scm.SCM.poll(SCM.java:373) athudson.model.AbstractProject._poll(AbstractProject.java:1471) athudson.model.AbstractProject.poll(AbstractProject.java:1404) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource) 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-15732) Duplicated / multiple Jenkins CLI entries under Manage Jenkins
Kannan Manickam assigned JENKINS-15732 to Kannan Manickam Duplicated / multiple Jenkins CLI entries under Manage Jenkins Change By: Kannan Manickam (06/Nov/12 9:37 AM) Assignee: KannanManickam 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-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Reynald Borer created JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 06/Nov/12 9:44 AM Description: Hi, I've the following NPE happening when scm-sync-configuration-plugin, making my Jenkins installation unusable (I've disabled this plugin). WARNING: Untrapped Error in Servlet java.lang.NullPointerException at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getInstance(ScmSyncConfigurationPlugin.java:272) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:25) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at
[JIRA] (JENKINS-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Reynald Borer updated JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Change By: Reynald Borer (06/Nov/12 9:45 AM) Environment: Jenkins1.489onDebianSqueeze,scm-sync-configuration-pluginversion0. 0. 6.1 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-15732) Duplicated / multiple Jenkins CLI entries under Manage Jenkins
Kannan Manickam commented on JENKINS-15732 Duplicated / multiple Jenkins CLI entries under Manage Jenkins It was a simple fix. Pull request sent: https://github.com/jenkinsci/jenkins/pull/607 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-15735) CVS Tag this build extremely slow
Olivier Chorier created JENKINS-15735 CVS Tag this build extremely slow Issue Type: Improvement Affects Versions: current Assignee: Unassigned Attachments: cvs-jk.GIF Components: cvs Created: 06/Nov/12 9:48 AM Description: After a build has been completed, it is possible to tag this build. I'm using CVS. After typing the tag name, heres the log : Build #190 Application d'un nom (tag) est en cours: Using locally configured password for connection to :pserver:***@**:/*** Using locally configured password for connection to :pserver:***@**:/*** Using locally configured password for connection to :pserver:***@**:/*** Using locally configured password for connection to :pserver:***@**:/*** etc. etc. Many many identical lines, about 2 per second. Tagging is extremely slow, in comparison with the same action using my Eclipse environment. Due Date: 06/Nov/12 12:00 AM Environment: Linux 2.6.24-16 i686 ; Jenkins 1.486 Project: Jenkins Labels: jenkins Priority: Major Reporter: Olivier Chorier 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-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Frédéric Camblor commented on JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Don't you have any other errors before this one ? Looking at source code the only potential NPE on this line is Hudson.getInstance() returns null ... which sounds really weird 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-15721) Cannot add browsers due to template include exception
Ian lee started work on JENKINS-15721 Cannot add browsers due to template include exception Change By: Ian lee (06/Nov/12 10:06 AM) 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-15736) Viewing performance report changes jvm locale
Karol Kański created JENKINS-15736 Viewing performance report changes jvm locale Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 06/Nov/12 10:07 AM Description: We have installed Locale Plugin to make all users see Jenkins in the same language but it sets locale only when saving configuration. Performance Plugin does it every time someone views performance report. This means that all users see Jenkins in the language of that person, which is particularly problematic when users come from different countries. Environment: Linux on 2.6.32-220.7.1.el6.x86_64 kernel, Jenkins 1.472, Performance Plugin 1.8 Project: Jenkins Labels: plugin Priority: Major Reporter: Karol Kański 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-15737) MultiJob plugin does not take account current parameters
Greg BOUGEARD created JENKINS-15737 MultiJob plugin does not take account current parameters Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 06/Nov/12 10:24 AM Description: since 1.6, multijob plugin does not pass current parameters to nested jobs. in 1.5 it was not possible to add in a phase job twice the same job (with different parameters), now it's fixed in 1.6 but the disability to pass current parameters is a really a show stopper for me. Project: Jenkins Priority: Critical Reporter: Greg BOUGEARD 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-15733) Mercurial plugin crashes when polling repository
Barbara Schael commented on JENKINS-15733 Mercurial plugin crashes when polling repository hello, The same happened to me. I upgraded the Jenkins and after two or three polling the same error popped up. 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-15702) InstantiationError: hudson.scm.AbstractCvs
David Ehrenberger updated JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs config.xml attached for a job that utilizes CVS. Since the warning doesn't indicate what job it applies to, this is just a guess. CVS plugin version is v2.6 Change By: David Ehrenberger (06/Nov/12 12:43 PM) Attachment: config.xml 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-15740) Report of CocoaPod Pods
Leif Janzik created JENKINS-15740 Report of CocoaPod Pods Issue Type: Improvement Assignee: Leif Janzik Components: CocoaPods Created: 06/Nov/12 1:44 PM Description: Create a Report of which Pods are resolved Project: Jenkins Priority: Major Reporter: Leif Janzik 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-15741) Make path to pod-executable configurable
Leif Janzik created JENKINS-15741 Make path to pod-executable configurable Issue Type: Improvement Assignee: Leif Janzik Components: CocoaPods Created: 06/Nov/12 1:45 PM Description: at the moment the plugin assumes, that "pod" is available directly. With this improvement the user can configure the path to the pod executable which should be used Project: Jenkins Priority: Major Reporter: Leif Janzik 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-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Pierre-Etienne Messier commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly Updated Jenkins to 1.489 and cppcheck plugin to 1.11 and the problem still persists. 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-15513) Invalid .ipa file
Christopher Orr commented on JENKINS-15513 Invalid .ipa file https://github.com/jenkinsci/ios-device-connector-plugin/pull/1 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-15744) Whitespaces at the end of input fields let to bogus file upload
Martin Heinemann created JENKINS-15744 Whitespaces at the end of input fields let to bogus file upload Issue Type: Bug Assignee: Unassigned Components: klaros-testmanagement Created: 06/Nov/12 3:59 PM Description: when giving strings with whitespaces at the end for project-id, SUT-ID or test env, the upload to klaros failes with invalid request. improvement would be to just make a trim on each string. Project: Jenkins Priority: Minor Reporter: Martin Heinemann 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-15744) Whitespaces at the end of input fields leads to bogus file upload
Martin Heinemann updated JENKINS-15744 Whitespaces at the end of input fields leads to bogus file upload Change By: Martin Heinemann (06/Nov/12 4:27 PM) Summary: Whitespacesattheendofinputfields let leads tobogusfileupload 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-12953) SVN Tag failing even though the Remote Module Location Tag Base URL values are correct
Jatin Tak commented on JENKINS-12953 SVN Tag failing even though the Remote Module Location Tag Base URL values are correct I am facing a similar problem with the plugin. Subversion copy failed. svn: File not found: revision 8286, path '/branches/samplePath/branches/samplePath' It is appending the path to itself. Any idea why this is happening and/or a workaround to this issue? 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-15727) JClouds Plug-In failing to start slave
Nathan Sharp commented on JENKINS-15727 JClouds Plug-In failing to start slave Sure enough! I found some logs in /var/log/auth.log mentioning attempted logins to root. Couldn't figure how how to have the plug-in log in via the 'ubuntu' user but still use the public key authentication. But by setting disable_root to 0 in /etc/cloud/cloud.cfg in my amazon image, I seem to be past that now I have a simple job running, but still having some problems. When the first job is queued, it starts a new amazon machine to service it. However if I put a second job in the queue, when it tries to start the second amazon machine I get this stack trace: [#|2012-11-06T11:48:08.801-0500|WARNING|oracle-glassfish3.1.1|hudson.slaves.NodeProvisioner|_ThreadID=26;_ThreadName=Thread-2;|Provisioned slave testaws failed to launch java.lang.NullPointerException at java.util.TreeMap.put(TreeMap.java:541) at java.util.TreeSet.add(TreeSet.java:238) at hudson.model.Node.getAssignedLabels(Node.java:240) at hudson.model.Slave.init(Slave.java:154) at hudson.model.Slave.init(Slave.java:132) at jenkins.plugins.jclouds.compute.JCloudsSlave.init(JCloudsSlave.java:47) at jenkins.plugins.jclouds.compute.JCloudsSlave.init(JCloudsSlave.java:70) at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:163) at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:216) at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:213) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) #] 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-15745) JClouds leaves cloud instances behind without cleaning them up
Nathan Sharp created JENKINS-15745 JClouds leaves cloud instances behind without cleaning them up Issue Type: Bug Assignee: abayer Components: jclouds Created: 06/Nov/12 5:08 PM Description: When failures happen during initialization, the plug-in often leaves behind unterminated instances even after all its cleanup. This could be costly See JENKINS-15727 for a couple different ways I've had failures. Usually it seems like the first machine it attempts to start works fine and terminates correctly. It is the second machine that it attempts to start that gets left behind. Environment: Jenkins 1.466.2, JClouds Plug-In 2.3.1, Ubuntu 12.04 x64. Connecting to Amazon EC2 trying to run an Ubuntu 12.04 image Project: Jenkins Priority: Major Reporter: Nathan Sharp 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-15727) JClouds Plug-In failing to start slave
abayer commented on JENKINS-15727 JClouds Plug-In failing to start slave Any chance you could attach the jclouds section of your config.xml? 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-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Joseph Benken commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs In 1.488, all my executors were dead. Stack trace from executors: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #1449 EXACT: lo=9,hi=7,size=10,size2=10 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:210) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:812) at hudson.model.Job.getEstimatedDuration(Job.java:819) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:320) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:303) at hudson.model.Queue.maintain(Queue.java:1033) at hudson.model.Queue.pop(Queue.java:861) at hudson.model.Executor.grabJob(Executor.java:284) at hudson.model.Executor.run(Executor.java:205) 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-13592) Details part of each ccm warning always displays all file
Pierre-Etienne Messier commented on JENKINS-13592 Details part of each ccm warning always displays all file Same here, using: Ubuntu 10.10 slave node 32 bits ccm version 1.1.6 Jenkins 1.489 CCM plugin 3.0 The metrics are good in the CCM XML file, for example: metric complexity143/complexity unitfocusNextItem()/unit classificationuntestable, very high risk/classification fileWidgets/QuickAccessBar/quickaccessbar.cpp/file startLineNumber248/startLineNumber endLineNumber675/endLineNumber SLOC427/SLOC /metric The report shows instead: quickaccessbar.cpp:0, Cyclomatic Complexity, Priority: High untestable, very high risk 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-15727) JClouds Plug-In failing to start slave
Nathan Sharp commented on JENKINS-15727 JClouds Plug-In failing to start slave If you give me your amazon user number, I can share the AMI with you. 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-15727) JClouds Plug-In failing to start slave
Nathan Sharp updated JENKINS-15727 JClouds Plug-In failing to start slave jclouds section of config.xml, with private key and authentication stuff removed. Change By: Nathan Sharp (06/Nov/12 6:51 PM) Attachment: configsnippet.xml 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-15727) JClouds Plug-In failing to start slave
abayer commented on JENKINS-15727 JClouds Plug-In failing to start slave Is that the account number? 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-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney commented on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell I put in a pull request for the fix: https://github.com/jenkinsci/ssh-slaves-plugin/pull/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-13091) java.io.StreamCorruptedException: invalid stream header: B055002D
Xavier Nodet commented on JENKINS-13091 java.io.StreamCorruptedException: invalid stream header: B055002D I would also be very interested in having this issue solved. Just saw it, using 1.456... 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-13091) java.io.StreamCorruptedException: invalid stream header: B055002D
Xavier Nodet edited a comment on JENKINS-13091 java.io.StreamCorruptedException: invalid stream header: B055002D I would also be very interested in having this issue solved. Just saw it, using 1.456... I would guess that the agent doesn't know that it's running under EBCDIC encoding... 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-15746) Cannot run SSH commands on SSH servers that use Windows shell
Jerry Maloney started work on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell Change By: Jerry Maloney (06/Nov/12 7:54 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-15727) JClouds Plug-In failing to start slave
Nathan Sharp commented on JENKINS-15727 JClouds Plug-In failing to start slave Thanks, you should have permission to access the AMI now. I just tried it again to make sure I wasn't crazy. This time I don't get any exceptions. According to the log it starts up 3 slaves on the cloud, but they don't appear in the GUI, and the tied job is still hanging. How is it supposed to differentiate different instances of the same "testaws" node? Again, thanks so much for your help. 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-15733) Mercurial plugin crashes when polling repository
Jesse Glick commented on JENKINS-15733 Mercurial plugin crashes when polling repository What Jenkins version? This looks like a core bug from what I can see so far. 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-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Dmitry Gil commented on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) The same issue with Jenkins 1.489 and TFS 1.20 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-15747) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas created JENKINS-15747 Logging all UpstreamCauses floods Jenkins in large setups Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 06/Nov/12 8:47 PM Description: In version 1.482 the feature "Report root causes of UpstreamCause in log and status pages" has been added. In certain scenarios (as stated below) this is absolutely not feasible because the amount of data logged per build might become dozens of megabytes. The result is that the jobs folder grows for several thousand builds in tens of gigabytes (within a couple of hours) which lets Jenkins hit memory limits and become unusable. Some more words on the scenario which shows that problem. We have a Jenkins instance with 30 executors, and about 5000 jobs. I think the specific thing is that these jobs are not independent (or slightly connected) but have a lot of up/downstream relationships. The problem is that when Jenkins hits one of the leaf jobs the list of hierarchic causes which triggered that job is tens of megabytes long (I am not attaching a full log I guess the content is pretty obvious). On the one hand because the nesting level is very high and on the other hand since there are several paths through the dependency graph. So there is an urgent need to optionally disable that feature. It basically makes Jenkins unusable in such scenarios. Project: Jenkins Priority: Critical Reporter: Dirk Thomas 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Mirko Raner commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Is there an ETA for this to be fixed? Or should I downgrade? To which version should I downgrade? 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-15748) fix Executor.interrupt(ABORTED) to let Groovy script cancle a build
Dirk Thomas created JENKINS-15748 fix Executor.interrupt(ABORTED) to let Groovy script cancle a build Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: core, groovy Created: 06/Nov/12 8:57 PM Description: It is currently not possible to cancel an ongoing build from a Groovy script. The feature is exposed in the UI where the user can cancel an ongoing build. This marks the build as ABORTED and stops the build immediately without processing any more build actions. Currently it is only possible from a Groovy script to either (1) interrupt the executor (but that marks the jobs a failed despite the arguments) or (2) mark a job aborted (but all build actions a processed). (1) build.getExecutor().interrupt(Result.ABORTED) This will mark the build failed, even if the API suggests something different. (2) build = Thread.currentThread().executable build.setResult(Result.ABORTED) Project: Jenkins Priority: Major Reporter: Dirk Thomas 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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. As you can see, I have $NODE_LABELS as a predefined parameter. Change By: Jason Stanley (06/Nov/12 9:16 PM) Attachment: Upstreamjobpredefinedparameters.jpg 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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley created JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Issue Type: Bug Assignee: huybrechts Attachments: Upstream job predefined parameters.jpg Components: parameterized-trigger Created: 06/Nov/12 9:14 PM Description: The value of "master" gets passed to the down stream job when you define NODE_LABELS in the Predefined parameters section of an upstream job. See attached screenshot showing the "Predefined parameters section" of the upstream job and the console output of the downstream job. Environment: Jenkins version 1.482 running on CentOS 5.8 Project: Jenkins Priority: Major Reporter: Jason Stanley 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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Please ignore first screenshot showing Predefined parameters section as the $NL was set incorrectly, it is now just NL=$NODE_LABELS. 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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. You can see the value for Node Label is "master". This is incorrect, see next screenshot for environment variable output from upstream build. Change By: Jason Stanley (06/Nov/12 9:24 PM) Attachment: Downstreamprojectconsoleoutput..jpg 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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
Jason Stanley updated JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Correct NODE_LABEL value from upstream build. Change By: Jason Stanley (06/Nov/12 9:28 PM) Attachment: NODE_LABELvaluefromupstreambuild..jpg 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-15487) External monitoring job exception java.lang.NoSuchMethodError: hudson.model.RunMap.put
Andres Suarez commented on JENKINS-15487 External monitoring job exception java.lang.NoSuchMethodError: hudson.model.RunMap.put It is happening on . 1.485 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-15750) Absolute path for local module directory
Claude Gan created JENKINS-15750 Absolute path for local module directory Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 07/Nov/12 2:40 AM Description: Why is absolute path not allowed when you specify the local module directory? I tried to specify one but it just creates it in the current workspace. e.g. scm class="hudson.scm.SubversionSCM" plugin="subversion@1.43" locations hudson.scm.SubversionSCM_-ModuleLocation remotehttps://puppet-svn.bfm.com/svn-repo/puppet/tags/prod_aladdin/remote local/local/file-repo/lab/local /hudson.scm.SubversionSCM_-ModuleLocation /locations We use Jenkins to compile Puppet catalogs. We do this for 3 OS types (ie RHEL6.3, RHEL5.8 and Solaris 10). We have 3 jobs setup to do the test against a common branch. This would be a headache for systems with limited disk space as the job would checkout the SVN branch three times. I was hoping we can specify an absolute path to optimize disk space. We have a workaround at the moment and this via symlinks. Environment: all Project: Jenkins Priority: Minor Reporter: Claude Gan 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-15751) Cannot escape dollar sign in Windows environment
Nick Grealy created JENKINS-15751 Cannot escape dollar sign in Windows environment Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 07/Nov/12 3:23 AM Description: Fix JENKINS-13566 introduced the following bug. I can no longer escape the dollar sign value on a Windows environment. e.g. foobar1=foo\$bar foobar2=foo$bar Respectively becomes: foo\$bar foo The value "foo$bar" cannot be achieved. My opinion is that the "escaping" behaviour should be the same regardless of operating system. I propose that the JENKINS-13566 changes should be reverted, and that Vincent Latombe should double escape his path. i.e. C:\DOCUME~1*\$NCESE~1\LOCALS~1\Temp Environment: EnvInject 1.71 Project: Jenkins Priority: Blocker Reporter: Nick Grealy 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-15751) Cannot escape dollar sign in Windows environment
Nick Grealy updated JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Nick Grealy (07/Nov/12 3:23 AM) Description: FixJENKINS-13566introducedthefollowingbug.IcannolongerescapethedollarsignvalueonaWindowsenvironment.e.g.foobar1=foo\$barfoobar2=foo$barRespectivelybecomes:foo\$barfooThevaluefoo$barcannotbeachieved.Myopinionisthattheescapingbehaviourshouldbethesameregardlessofoperatingsystem.IproposethattheJENKINS-13566changesshouldbereverted,andthatVincentLatombeshoulddoubleescapehispath.i.e.C:\DOCUME~1 * \ * \$NCESE~1\LOCALS~1\Temp 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-15751) Cannot escape dollar sign in Windows environment
Nick Grealy updated JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Nick Grealy (07/Nov/12 3:28 AM) Description: FixJENKINS-13566introducedthefollowingbug.IcannolongerescapethedollarsignvalueonaWindowsenvironment.e.g.foobar1=foo\$barfoobar2=foo$barRespectivelybecomes:foo\$barfooThevaluefoo$barcannotbeachieved.Myopinionisthattheescapingbehaviourshouldbethesameregardlessofoperatingsystem.IproposethattheJENKINS-13566changesshouldbereverted,andthatVincentLatombeshoulddoubleescape his their path.i.e.C:\DOCUME~1\\$NCESE~1\LOCALS~1\Temp 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-15752) Menggunakan Internet Secara Positif
Antoq rose created JENKINS-15752 Menggunakan Internet Secara Positif Issue Type: Bug Assignee: kutzi Components: instant-messaging Created: 07/Nov/12 4:42 AM Description: Menggunakan Internet Secara Positif Assalamualaikum, wr. wb Selamat sore sobat semua, semoga selalu sehat selalu dan dalam rahmat dari Allah, pada kali ini saya akan memposting sebauh artikel tentang Menggunakan Internet Secara Positif. kenapa posting itu yang saya tulis??? mungkin dari pembac. Project: Jenkins Labels: internet, free access Priority: Major Reporter: Antoq rose 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-14785) Add support for slicing matrix job configuration
hiteswar kumar commented on JENKINS-14785 Add support for slicing matrix job configuration i think below example could be useful to understand slicing "matrix(multi-configuration) jobs" change label|slave name for matrix(multi-configuration) job- not changed if using "Evaluate Tied Label Slicer " because matrix job not having option “Restrict where this project can be run” to tie label. Here label/slaves tied at axis. is this useful!!! 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
