[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Wannes Sels started work on JENKINS-25639 Multiple builds can be triggered for same commit Change By: Wannes Sels (21/Nov/14 8:27 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Wannes Sels commented on JENKINS-25639 Multiple builds can be triggered for same commit See test case in pull request 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes @Jordan Is it possible to show us the vcard stanza that Smack sends to the server? One could assume that the server sends the 'internal-server-error', and subsequently closes the connection, because of the stanza. Also some logs from the the server side may be helpful to determine the underlying issue. I've no reports that Smack's 4 vcard implementation is broken in this regard, but I'm of course eager to resolve such issues. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus edited a comment on JENKINS-25676 Disconnect from XMPP after a few minutes @Jordan Is it possible to show us the vcard stanza that Smack sends to the server? The interesting part of the logs is actually just before the part you showed us . One could assume that the server sends the 'internal-server-error', and subsequently closes the connection, because of the stanza. Also some logs from the the server side may be helpful to determine the underlying issue. I've no reports that Smack's 4 vcard implementation is broken in this regard, but I'm of course eager to resolve such issues. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Kanstantsin Shautsou commented on JENKINS-25639 Multiple builds can be triggered for same commit Your test case tests only your invented Set replacement and not a polling/build triggering. Please provide a real use case from practice. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25724) Changes doesn't show unshelved files
Morne Joubert
created JENKINS-25724
Changes doesnt show unshelved files
Issue Type:
Task
Assignee:
Unassigned
Components:
p4-plugin
Created:
21/Nov/14 9:30 AM
Description:
I have written a tool that plugs into P4V that allows the user to selected a shelved CL and trigger a Jenkins job.
I trigger the jobs remotely adding the following 2 parameters (to all the other parameters)
review=shelved CL number from P4V
status=shelved
From the example below, i can see the job does a sync and then does the unshelve
SCM Task: syncing files at change: 73544
... sync c:\jenkins2\workspace_sdmos_sdmos-int_3/...@73544
... force update false
... bypass have false
SCM Task: unshelve review: 73478
... sync c:\jenkins2\workspace_sdmos_sdmos-int_3/...
... unshelve -f -s 73478 c:\jenkins2\workspace_sdmos_sdmos-int_3/...
... revert -k c:\jenkins2\workspace_sdmos_sdmos-int_3/...
listing changes: //__sdmos_sdmos-int_3_jenkins_p4_mlb-gb-mlb-dt-007/...@73478,73544
so far so good.
But when i look at the changes pages the unshelved changes are missing.
I do get a
"No connection to Perforce." entry in the changes.
Looking at the code:
in the P4ChangeSet\index.jelly
I can see:
j:forEach var="entry" items="${it.history}" varStatus="loop"
j:choose
j:when test="${entry.id == null}"
No connection to Perforce.
/j:when
Please note that i am not using the "Review" action.
So:
1) Either there is a bug
2) Me triggering the job remotely using review+status=shelved is incorrect
Project:
Jenkins
Priority:
Minor
Reporter:
Morne Joubert
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Wannes Sels commented on JENKINS-25639 Multiple builds can be triggered for same commit My test case shows that DefaultBuildChooser().getCandiateRevisions() can return the same commit twice. GitSCM.determineRevisionToBuild() will schedule another build for that same commit. That next build will arrive at the same situation again, resulting in infinite build loop. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build
Tomer Galun assigned JENKINS-21241 to Tomer Galun Plugin should expose environment variables to tell how many times naginator has restarted the build Change By: Tomer Galun (21/Nov/14 9:42 AM) Assignee: NicolasDeLoof TomerGalun 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
alexanderlink commented on JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. We could not reproduce this issue with Jenkins 1.577, Gerrit Trigger 2.11.1, Git Client 1.10.1 and Git Plugin 2.2.5. The Gerrit Trigger plugin automatically reconnected to the Gerrit Server. Any further pushes to Gerrit resulted in properly triggered Gerrit voter jobs. We also tested Gerrit shutdown while a Gerrit voter job was in the build step. Of course the Gerrit Trigger plugin could not vote when the job finished. This voting is lost. And the Gerrit Trigger plugin did not trigger the voter job for this patch set again, but it has been triggered for all new patch sets. And for the lost patch set a manual retrigger worked as well. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Kanstantsin Shautsou commented on JENKINS-25639 Multiple builds can be triggered for same commit How it will work with cherry-picked to other branch commits? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-25698) Archiving artifacts (or FilePath operatons) should properly time out and retry the copy
Daniel Beck commented on JENKINS-25698 Archiving artifacts (or FilePath operatons) should properly time out and retry the copy There are plugins that can tolerate master/slave disconnects during job execution. Note that there are already issues in this tracker requesting more network issue tolerance. If this is just going to be the same issue, this should be resolved as duplicate. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build
Kanstantsin Shautsou commented on JENKINS-21241 Plugin should expose environment variables to tell how many times naginator has restarted the build Better do NAGINATOR_* vars. How this will work with parallel builds? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Wannes Sels commented on JENKINS-25639 Multiple builds can be triggered for same commit Cherry-picked commit = new commit with new sha1 That should be picked up like any other commit 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20562) Polling with Included Region only trigger a single job
Fredric Lonngren commented on JENKINS-20562 Polling with Included Region only trigger a single job I have tried this again with Jenkins ver. 1.590 an now it works. Both jobs with the same include regions trigger and builds as expected. This issue can be closed. Nov 21, 2014 10:42:12 AM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Triggering the polling of FL_TriggTest Nov 21, 2014 10:42:12 AM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Triggering the polling of FL_TriggTest2 Nov 21, 2014 10:42:12 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in FL_TriggTest. Triggering #17 Nov 21, 2014 10:42:13 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in FL_TriggTest2. Triggering #11 Nov 21, 2014 10:42:22 AM INFO hudson.model.Run execute FL_TriggTest2 #11 main build action completed: SUCCESS Nov 21, 2014 10:42:22 AM INFO hudson.model.Run execute FL_TriggTest #17 main build action completed: SUCCESS 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20562) Polling with Included Region only trigger a single job
Fredric Lonngren edited a comment on JENKINS-20562 Polling with Included Region only trigger a single job I have tried this again with Jenkins ver. 1.590 Git plugin 2.3 and now it works. Both jobs with the same include regions trigger and builds as expected. This issue can be closed. Nov 21, 2014 10:42:12 AM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Triggering the polling of FL_TriggTest Nov 21, 2014 10:42:12 AM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Triggering the polling of FL_TriggTest2 Nov 21, 2014 10:42:12 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in FL_TriggTest. Triggering #17 Nov 21, 2014 10:42:13 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in FL_TriggTest2. Triggering #11 Nov 21, 2014 10:42:22 AM INFO hudson.model.Run execute FL_TriggTest2 #11 main build action completed: SUCCESS Nov 21, 2014 10:42:22 AM INFO hudson.model.Run execute FL_TriggTest #17 main build action completed: SUCCESS 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-25725) Bad performance: 10 minutes for parsing 2MB of data
rggjan created JENKINS-25725 Bad performance: 10 minutes for parsing 2MB of data Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 21/Nov/14 10:16 AM Description: The log parser plugin has extremely bad performance for some reason. Parsing 2MB of logs takes around 10 minutes usually (on a pretty decent server) Is this normal? Can you reproduce this? Project: Jenkins Priority: Major Reporter: rggjan 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-25725) Bad performance: more than 5 minutes for parsing 2MB of data
rggjan updated JENKINS-25725 Bad performance: more than 5 minutes for parsing 2MB of data Change By: rggjan (21/Nov/14 10:40 AM) Summary: Badperformance: 10 morethan5 minutesforparsing2MBofdata Description: Thelogparserpluginhasextremelybadperformanceforsomereason.Parsing2MBoflogstakes around10 morethan5 minutesusually(onaprettydecentserver)Isthisnormal?Canyoureproducethis? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-restrictions-plugin] (JENKINS-25726) Add started by a user JobRestriction
Oleg Nenashev created JENKINS-25726 Add started by a user JobRestriction Issue Type: Bug Assignee: Oleg Nenashev Components: job-restrictions-plugin Created: 21/Nov/14 10:45 AM Description: See the discussion in https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin?focusedCommentId=74875980#comment-74875980 Project: Jenkins Priority: Minor Reporter: Oleg Nenashev 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Kristofer Lundgren commented on JENKINS-14276 Git SCM-polling doesnt work when using a parametrized branch-name Bug still exist in git plugin 2.3 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
Ireneusz Makowski commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Could you please add this also to lts? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25074) Build health computed twice per job
Ireneusz Makowski commented on JENKINS-25074 Build health computed twice per job could you please add this to LTS? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-restrictions-plugin] (JENKINS-25726) Add started by a user JobRestriction
Oleg Nenashev updated JENKINS-25726 Add started by a user JobRestriction Change By: Oleg Nenashev (21/Nov/14 10:58 AM) Issue Type: Bug NewFeature 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
valentina armenise created JENKINS-25727 parallel steps of workflow executions randomly fail Issue Type: Bug Assignee: Unassigned Components: workflow-plugin Created: 21/Nov/14 11:01 AM Description: org.jenkinsci.plugins.workflow.cps.steps.ParallelStepException: Parallel step long running test task failed at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:126) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:105) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:295) at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:262) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:172) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: hudson.AbortException: script returned exit code -1 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:205) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) ... 3 more Finished: FAILURE Environment: Jenkins ver. 1.580.1.1-beta-6 (Jenkins Enterprise by CloudBees 14.11) Project: Jenkins Labels: parallel workflow Priority: Minor Reporter: valentina armenise 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Kristofer Lundgren reopened JENKINS-14276 Git SCM-polling doesnt work when using a parametrized branch-name I would really appreciate if you (Mark) applied this patch to git plugin 2.3 as well. Change By: Kristofer Lundgren (21/Nov/14 11:09 AM) Resolution: Fixed Status: Closed Reopened Assignee: NicolasDeLoof MarkWaite 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
Kohsuke Kawaguchi
updated JENKINS-25727
parallel steps of workflow executions randomly fail
Change By:
Kohsuke Kawaguchi
(21/Nov/14 11:13 AM)
Description:
{noformat}
org.jenkinsci.plugins.workflow.cps.steps.ParallelStepException:Parallelsteplongrunningtesttaskfailed atorg.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:126) atorg.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:105) atorg.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:295) atcom.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68) atcom.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) atcom.cloudbees.groovy.cps.Next.step(Next.java:58) atcom.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145) atorg.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:262) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174) atorg.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:172) atorg.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) athudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:744)Causedby:hudson.AbortException:scriptreturnedexitcode-1 atorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:205) atorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:159) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) ...3moreFinished:FAILURE
{noformat}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
Kohsuke Kawaguchi commented on JENKINS-25727 parallel steps of workflow executions randomly fail The fake exit code "-1" signifies that the process has disappeared without leaving the exit code file behind. Looking into why this is the case. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
Kohsuke Kawaguchi commented on JENKINS-25727 parallel steps of workflow executions randomly fail valentina armenise confirmed that the master and a slave has a large latency between them, and that the issue happens about once in 10. So the race condition hypothesis feels more feasible. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25728) latest test results not shown in project when last build failed
Kanstantsin Shautsou created JENKINS-25728 latest test results not shown in project when last build failed Issue Type: Bug Assignee: teilo Components: cucumber-testresult-plugin Created: 21/Nov/14 11:42 AM Description: Keeping it here, will investigate later. No test reports that matches acceptance-test/build/results/test_results.js found. Configuration error? Build step 'Publish Cucumber test result report' changed build result to FAILURE Then project page has no "latest test results" link at all. Also it maybe be a good idea to print cucumber-testresult before this messages printed to listener like it do htmlpublisher. Project: Jenkins Priority: Minor Reporter: Kanstantsin Shautsou 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25702) Fail Build if warnings are present is not working for first build or build without any reference
aravind valluri commented on JENKINS-25702 Fail Build if warnings are present is not working for first build or build without any reference Hi, I am using Warnings Plugin Release 4.33 and analysis collector 1.37 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-25729) Result files are identified by the file name, not by the URL
René Kugel created JENKINS-25729 Result files are identified by the file name, not by the URL Issue Type: Improvement Assignee: Manuel Carrasco Attachments: jenkins_results.png Components: performance-plugin Created: 21/Nov/14 12:21 PM Description: Consider the situation in jenkins_results.png If there are more than one result files with the same filename but a different URL, there will be only one graphical representation in the PerformanceReport UI. Result files should be identified by the URL. Project: Jenkins Priority: Minor Reporter: René Kugel 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [regression-report-plugin] (JENKINS-25730) java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction;
Vinicius Suyama created JENKINS-25730 java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; Issue Type: Bug Assignee: Kengo TODA Components: regression-report-plugin Created: 21/Nov/14 12:29 PM Description: ERROR: Publisher jp.skypencil.jenkins.regression.RegressionReportNotifier aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at jp.skypencil.jenkins.regression.RegressionReportNotifier.perform(RegressionReportNotifier.java:97) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Project: Jenkins Priority: Minor Reporter: Vinicius Suyama 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [regression-report-plugin] (JENKINS-25730) java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction;
Vinicius Suyama updated JENKINS-25730 java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; Change By: Vinicius Suyama (21/Nov/14 12:30 PM) Environment: Jenkins1.590 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-25698) Archiving artifacts (or FilePath operatons) should properly time out and retry the copy
trejkaz commented on JENKINS-25698 Archiving artifacts (or FilePath operatons) should properly time out and retry the copy It was reported as a specific issue, just in case it's possible to fix this one issue without fixing the whole core of Jenkins. Well over 90% of our "build failures" (actually Jenkins-fails, not build failures) happen during the copying of files in one direction or the other, so even fixing this one issue would improve things enormously. (Hell will probably freeze over before Jenkins devs start to care about reliability of the architecture itself. Many years have passed with no improvements in that area whatsoever, so I have no reason to start believing in it at this point in time.) If there are any plugins which can tolerate disconnects during job execution, they appear to be missing from the list. https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Slavelaunchersandcontrollers 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25731) Introduce a Jenkins URL aliases parameter in configuration settings
Torsten Schlabach created JENKINS-25731 Introduce a Jenkins URL aliases parameter in configuration settings Issue Type: Improvement Assignee: Unassigned Components: core Created: 21/Nov/14 1:00 PM Description: Obviously, something has changed in 1.572 when it comes to Jenkins generating URLs referring to itself, as explained here: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken In practice, of course, the "Jenkins URL" parameter should be properly set. Yet in cases where there is more than one possible URL to reach Jenkins (for whatever reasons one can imagine) Jenkins still worked 99% for us even if we accessed it using a different URL than the one in that parameter. As that behaviour has changed, for situations where there is a good reason to keep more than one possible URL, wouldn't a 2nd field there "Jenkins URL aliases" with out without redirecting make sense. (Redirect = when accessed through an alias, redirect to the one and only URL / other model: When accessed at www.alias2.url/jenkins make self-referring links also point to www.alias2.url/jenkins. Bonus question: In http://stackoverflow.com/questions/11221238/what-does-jenkins-url-means-in-configuration-settings in one of the answers it says: "Jenkins can't determine its URL on its own" Actually, why not? Besides doing a hostname and port lookup (which indeed can lead to wrong results) shouldn't the URL used to access the page be available in the HTTP headers for any one request? Project: Jenkins Priority: Minor Reporter: Torsten Schlabach 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25702) Fail Build if warnings are present is not working for first build or build without any reference
Ulli Hafner resolved JENKINS-25702 as Fixed Fail Build if warnings are present is not working for first build or build without any reference Already fixed in 4.44. Change By: Ulli Hafner (21/Nov/14 1:26 PM) Status: Open Resolved Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25702) Fail Build if warnings are present is not working for first build or build without any reference
Ulli Hafner edited a comment on JENKINS-25702 Fail Build if warnings are present is not working for first build or build without any reference Already fixed in 4.34. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25516) Prepare for Shutdown and Restart When Installing New Plugin
Helder Breda stopped work on JENKINS-25516 Prepare for Shutdown and Restart When Installing New Plugin Change By: Helder Breda (21/Nov/14 1:41 PM) Status: InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25516) Prepare for Shutdown and Restart When Installing New Plugin
Helder Breda started work on JENKINS-25516 Prepare for Shutdown and Restart When Installing New Plugin Change By: Helder Breda (21/Nov/14 1:41 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25731) Introduce a Jenkins URL aliases parameter in configuration settings
Daniel Beck commented on JENKINS-25731 Introduce a Jenkins URL aliases parameter in configuration settings Seems like it would just add additional options while providing no real value. "Jenkins can't determine its URL on its own" Actually, why not? Besides doing a hostname and port lookup (which indeed can lead to wrong results) shouldn't the URL used to access the page be available in the HTTP headers for any one request? Not everything Jenkins does is in the context of a request. For example, the JENKINS_URL or BUILD_URL variables defined inside builds. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25731) Introduce a Jenkins URL aliases parameter in configuration settings
Daniel Beck commented on JENKINS-25731 Introduce a Jenkins URL aliases parameter in configuration settings Another common case would be the links in the build failure notifications. No HTTP request anywhere. Note that supporting different Jenkins URLs opens a whole can of worms, e.g. wrt cookies. You click a link sent by a colleague (who prefers the IP address he's always used over the nice server name) and you go WHY AM I NOT LOGGED IN? THIS IS BULL! Of course, the same issue occurs today, but I expect that with the alias feature comes an expectation that things like this "just work". 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
mdelaney created JENKINS-25732 NPE Thrown when using the parameterize build with a Run Parameter Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 21/Nov/14 2:28 PM Description: After updating to 1.3.29, we noticed that when we have jobs with the 'Run Parameter', the Perforce plug-in throws a NPE when trying to calculate the effective workspace name. The stack trace printed out by Jenkins is a: sample-run-parameter-job $ p4 workspace -o sample-run-parameter-job Caught exception in perforce-plugin. nulljava.lang.NullPointerException at java.lang.String.replace(String.java:2219) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:185) at hudson.plugins.perforce.utils.MacroStringHelper.getDefaultSubstitutions(MacroStringHelper.java:341) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:246) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:298) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:148) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:876) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) ERROR: Caught exception in perfoce-plugin. null Environment: Jenkins 1.565.3 OS: Ubuntu 12.04 LTS (x68) Perforce Server: 14.1 Project: Jenkins Priority: Major Reporter: mdelaney 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-25733) Regex multiline support
Judith Gmeiner created JENKINS-25733 Regex multiline support Issue Type: Improvement Assignee: huybrechts Components: description-setter-plugin Created: 21/Nov/14 2:45 PM Description: The limitation that multiline regular expressions aren't supported and only the first match is taken for the description, makes this plugin useless for us. Please add multiline support! Project: Jenkins Priority: Minor Reporter: Judith Gmeiner 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24589) Build History - name and links overlap if build names are long
Micheal Schexnayder commented on JENKINS-24589 Build History - name and links overlap if build names are long I've been seeing this as well. I've tried setting the names to something as short (and still descriptive) as possible, but after upgrading to 590 I'm still seeing the overlap. I use single jobs to build from multiple branches of the same product with a branch monicker in the buildname (via build name setter plugin) as a way to differentiate them for my users. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24322) SCM pooling triggers builds one after another and never stops
Dane Powell commented on JENKINS-24322 SCM pooling triggers builds one after another and never stops Sounds like https://issues.jenkins-ci.org/browse/JENKINS-25639 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24589) Build History - name and links overlap if build names are long
Steve Haworth commented on JENKINS-24589 Build History - name and links overlap if build names are long Yes I get this behaviour with post build annotation we put into description. It looks really bad and unprofessional. Comments I frequently get now from Senior management, are "Why don't you get a professionally created tool"? With this on the UI, it looks like a typical "hacky Open Source" project. I don't know why anyone bothered to update the UI. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25734) Massive executors death on a node, causeOfDeath is null
Oleg Nenashev created JENKINS-25734 Massive executors death on a node, causeOfDeath is null Issue Type: Bug Assignee: Unassigned Components: core Created: 21/Nov/14 3:32 PM Description: Executors started dying on one node with unknown reason. Other nodes are not affected According to Jenkins UI, all executors (excepting ones with a running build) continuously die and restore No error info even on the FINEST log level Executor::causeOfDeath field is null when I open the death descriptor causeOfDeath page is accessible, hence Executor::isAlive() returns false Probably, a node user decreased the number of executors (to be checked) WARNING: Caught exception evaluating: h.printThrowable(it.causeOfDeath) in /computer//executors/4/causeOfDeath. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.Functions.printThrowable(Functions.java:1184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) Environment: Jenkins-1.532 JNLP slaves Project: Jenkins Priority: Major Reporter: Oleg Nenashev 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25734) Massive executors death on a node, causeOfDeath is null
Oleg Nenashev commented on JENKINS-25734 Massive executors death on a node, causeOfDeath is null The code has been reworked in https://github.com/jenkinsci/jenkins/commit/73073387c85d90bb5543a856af24bfcb5590352a I'm not sure the issue may happen in newest core versions. BTW, it makes sense to handle NPE at least 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
Rob Petti assigned JENKINS-25732 to Oleg Nenashev NPE Thrown when using the parameterize build with a Run Parameter Change By: Rob Petti (21/Nov/14 3:47 PM) Assignee: RobPetti OlegNenashev 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25734) Massive executors death on a node, causeOfDeath is null
Oleg Nenashev commented on JENKINS-25734 Massive executors death on a node, causeOfDeath is null Created PR: https://github.com/jenkinsci/jenkins/pull/1468 (WiP) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25734) Massive executors death on a node, causeOfDeath is null
Oleg Nenashev assigned JENKINS-25734 to Oleg Nenashev Massive executors death on a node, causeOfDeath is null Change By: Oleg Nenashev (21/Nov/14 3:50 PM) Assignee: OlegNenashev 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker updated JENKINS-25676 Disconnect from XMPP after a few minutes Change By: Jordan Spiker (21/Nov/14 3:52 PM) Attachment: jenkins_im_redacted.txt 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes @Forian I'm uploading as much as I can get from the FINEST level log. Please let me know if I can provide more info. Note that I have redacted sensitive information. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes It is unlikely that I would be able to get logs from the IM server any time soon. Our sysadmins are very busy with higher priority tasks. If that is required to help fix this issue then I can hopefully get some logs in the next week or two. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
Oleg Nenashev started work on JENKINS-25732 NPE Thrown when using the parameterize build with a Run Parameter Change By: Oleg Nenashev (21/Nov/14 3:56 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-25698) Archiving artifacts (or FilePath operatons) should properly time out and retry the copy
Daniel Beck commented on JENKINS-25698 Archiving artifacts (or FilePath operatons) should properly time out and retry the copy Commercial Jenkins Enterprise has http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/long-running-build.html The upcoming https://github.com/jenkinsci/workflow-plugin (no wiki yet) also supports connection aborts. https://wiki.jenkins-ci.org/display/JENKINS/Durable+Task+Plugin can be used by plugins to add support for more resilient builds Admittedly, they're all far from mature, or transparent to users. It's a rather recent effort. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
Oleg Nenashev commented on JENKINS-25732 NPE Thrown when using the parameterize build with a Run Parameter The method getsEnvVars, where key or value is null. I suppose it is an issue in Run Parameter, but it makes sense to protect Perforce plugin from it 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-25735) Mask Passwords doen't mask Credentials Parameter
Marshall GSEIT
created JENKINS-25735
Mask Passwords doent mask Credentials Parameter
Issue Type:
Bug
Assignee:
Daniel Petisme
Components:
mask-passwords-plugin
Created:
21/Nov/14 4:34 PM
Description:
After installing Mask Passwords Plugin 2.7.2, it allows the system configuration to set the passwords to be masked. One of which is Credentials Parameter.
However, in a project, if mask passwords is selected and an existing credential is used in the build step, the information is still displayed plaintext within the console output.
Steps To Reproduce:
Configure System
Mask Passwords - Parameters to automatically mask
x Non-Stored Password Parameter
x Credentials Parameter
x Password Parameter
Mask Passwords - Global name/password pairs
None added.
I already have several "Username with password" Global credentials
Create freestyle project
x Mask passwords (and enable global passwords)
Responce: Password Parameters, or any other type of build parameters selected for masking in Hudson's/Jenkins' main configuration screen (Manage Hudson Configure System), will be automatically masked.
x Use secret text(s) or file(s)
Add: Username and password
Variable: oracleCredential
Credentials
*) Specific credentials
my_oracle_username/* (Oracle remote login)
parameter _expression_: ${oracleCredential}
Add build step: Execute Windows batch command
Command: @echo %oracleCredential%
Save
Build Now, and examine Console Output
Expected: ** is displayed in place of %oracleCredential%
Actual:Actual username:password value of %oracleCredential% is displayed.
Environment:
Jenkins 1.580.1 running as a Windows service
Windows Server 2008 R2 SP1 64-bit
Firefox 33.1.1
Plugins: (abbreviated list)
* Credentials Binding Plugin 1.2
* Credentials Plugin 1.18
* Plain Credentials Plugin 1.0
* SSH Credentials Plugin 1.10
* Mask Passwords Plugin 2.7.2
Project:
Jenkins
Labels:
plugin,
jenkins,
security,
credentials,
mask-passwords
Priority:
Minor
Reporter:
Marshall GSEIT
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25736) Ability to pause a running flow
Jesse Glick created JENKINS-25736 Ability to pause a running flow Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 21/Nov/14 4:35 PM Description: For some purposes it is useful to pause a running flow so you can investigate an ongoing problem and maybe try to fix it before resuming, rather than having to retry the whole flow (or from a checkpoint). The minimal feature would be for the CPS VM to be paused between steps. This is probably an easy enhancement, with an API needed just to expose this action in the UI somewhere. Better would be if a StepExecution (an active head) could be paused. That would be another API change. The most interesting case is DurableTaskStep.Execution; for that to work we would need to also add an API to Controller in durable-task asking it to pause the process if possible. On Unix this would be SIGSTOP (later SIGCONT); not sure if there is any Windows equivalent. Project: Jenkins Priority: Major Reporter: Jesse Glick 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25074) Build health computed twice per job
Jesse Glick updated JENKINS-25074 Build health computed twice per job Change By: Jesse Glick (21/Nov/14 4:39 PM) Labels: health lts-candidate performanceview 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
Jesse Glick updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Change By: Jesse Glick (21/Nov/14 4:39 PM) Labels: lock lts-candidate performancethreads 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25732) NPE Thrown when using the parameterize build with a 'Run Parameter'
mdelaney commented on JENKINS-25732 NPE Thrown when using the parameterize build with a Run Parameter I completely agree. This seems more like a bug in the 'Run Parameter' plugin but thought the plug-in should offer some type of protection. I'm working on drafting up a bug for the Run Parameter plug-in but like you, I'm not sure where this gets injected so I'm researching that. The value for this variable eventually gets set but just after the SCM phase has already passed. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25691) Redeploy link is displayed to Anonymous users with read only permissions for a job
Jesse Glick resolved JENKINS-25691 as Fixed Redeploy link is displayed to Anonymous users with read only permissions for a job I guess the JIRA link daemon is down again. Change By: Jesse Glick (21/Nov/14 4:49 PM) Status: Open Resolved Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
Patrik Boström resolved JENKINS-25457 as Fixed Server error when viewing pipeline with NOT_BUILT result job. Change By: Patrik Boström (21/Nov/14 4:53 PM) Status: Open Resolved Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
Patrik Boström stopped work on JENKINS-25457 Server error when viewing pipeline with NOT_BUILT result job. Change By: Patrik Boström (21/Nov/14 4:53 PM) Status: InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
Patrik Boström commented on JENKINS-25457 Server error when viewing pipeline with NOT_BUILT result job. Merged to master 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started.
Mike Delaney created JENKINS-25737 Run Parameter build parameter is null when SCM/pre-SCM phase is started. Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-11-21 at 12.07.09 PM.png Components: core Created: 21/Nov/14 5:09 PM Description: When using the 'Run Parameter' build parameter type, the value of this parameter is NULL when the SCM phase is started. This can lead to Null Pointer Exception when trying to reference said variable during your SCM execution, or pre-SCM execution build step. Environment: Jenkins v1.565.3 Operating System: Ubuntu 12.04LTS Project: Jenkins Priority: Minor Reporter: Mike Delaney 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes Thanks Jordan for your detailed feedback. Reading the logs and reviewing the issue again, I begin to doubt that this is related to vcard in any way. At least there are no proofs that this is caused by the vcard code. The only hint towards vcard appears in the stacktrace, but this could be pure coincidence. After all it's the server who was closing the connection. The server logs from the relevant time period would sure be helpful. So I don't think that the internal-server-error exception is related to the connection termination at all. What likely happened is that createVCard in JabberIMConnection:537 threw an internal-server-error XMPPException, but this does not mean that the connection will get closed. This only means that the server responded to the vcard IQ request from the client, with an IQ error. The timestamps also strengthen this thesis: the XMPPException is at 5:17:45, but the closing stream elements are send at 5:27:23. @Jordan I think the answer, or at least helpful information what is going on, is found in the server logs (under the assumption that it's the server who is terminating the connection, the timestamps give no clear indication who sends the closing stream element first). @kutzi I recommend reverting the related change and reopening 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20046) Massive Jenkins slowdown when jobs in Queue (due to Queue.maintain())
Martin Schröder commented on JENKINS-20046 Massive Jenkins slowdown when jobs in Queue (due to Queue.maintain()) Hi Hans-Jürgen. Yes, we're currently preparing a patch against 1.580.1. It will include the improved locking mechanism and some further changes to optimize the speed of the Queue maintenance (Queue.maintain()). Additionally, we're preparing a (completely separate) patch and pull request to completely overhaul the scheduling logic. Basically, the current Queue.maintain() algorithm scales O(m*n), where m is the number of (non-blocked) jobs in the queue and n is the number of (non-busy) executors in the system. When you have a long queue and many executors, this function essentially life-locks, taking several seconds to finish. It is also inherently sequential, only one thread can do this at a time. And then, to complete the 1-2-knockout punch, you must remember that EVERY executor needs to run a Queue.maintain() before it can mark itself as free. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20046) Massive Jenkins slowdown when jobs in Queue (due to Queue.maintain())
Martin Schröder edited a comment on JENKINS-20046 Massive Jenkins slowdown when jobs in Queue (due to Queue.maintain()) Hi Hans-Jürgen. Yes, we're currently preparing a patch against 1.580.1. It will include the improved locking mechanism and some further changes to optimize the speed of the Queue maintenance (Queue.maintain()). Additionally, we're preparing a (completely separate) patch and pull request to completely overhaul the scheduling logic. Basically, the current Queue.maintain() algorithm scales O(m*n), where m is the number of (non-blocked) jobs in the queue and n is the number of (non-busy) executors in the system. When you have a long queue and many executors, this function essentially life-locks, taking several seconds to finish. It is also inherently sequential, only one thread can do this at a time. And then, to complete the 1-2-knockout punch, you must remember that EVERY executor needs to run a Queue.maintain() before it can mark itself as free. Taking all of this together, this means that Queue.maintain() is currently the biggest hurdle for scaling up Jenkins. And without the patch above, the Web UI also completely locks up, as even the read functions needed to display the index page have to wait for Queue.maintain() to finish! Best regards, Martin. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
Jesse Glick updated JENKINS-25727 parallel steps of workflow executions randomly fail Change By: Jesse Glick (21/Nov/14 5:39 PM) Labels: parallel workflow 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
Jesse Glick assigned JENKINS-25727 to Jesse Glick parallel steps of workflow executions randomly fail Change By: Jesse Glick (21/Nov/14 5:39 PM) Assignee: JesseGlick 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-25738) Add Whitelisted methods to get the build result
Brian Krische created JENKINS-25738 Add Whitelisted methods to get the build result Issue Type: Improvement Assignee: wolfs Components: groovy-postbuild-plugin Created: 21/Nov/14 5:41 PM Description: Some of my post build scripts perform different actions depending on the build result. With the new security updates introduced in 2.0, there are no whitelisted methods of retrieving the build result. Project: Jenkins Priority: Minor Reporter: Brian Krische 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Jesse Glick updated JENKINS-25727 Occasional exit status -1 with long latencies Change By: Jesse Glick (21/Nov/14 5:40 PM) Summary: parallelstepsofworkflowexecutionsrandomlyfail Occasionalexitstatus-1withlonglatencies Component/s: durable-task-plugin Component/s: workflow-plugin 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Ray Sennewald commented on JENKINS-25111 Ability to Copy Artifacts from a Phase Job Yes but that isn't the case. We have phase jobs which run on different servers, so this solution won't work. I have an open Pull Request for implementing this functionality here: https://github.com/jenkinsci/tikal-multijob-plugin/pull/54, I just need to get the tests passing and then hopefully they will merge it in . 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-2670) Error 404 for multi-configuration projects when values contains a slash '/'
krizleebear reopened JENKINS-2670 Error 404 for multi-configuration projects when values contains a slash / I just observed exactly this issue with Jenkins LTS version 1.580.1 Do you need more information on this? I'm happy to help. Change By: krizleebear (21/Nov/14 5:55 PM) Resolution: Fixed Status: Closed Reopened 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-25735) Mask Passwords doen't mask Credentials Parameter
Daniel Beck updated JENKINS-25735 Mask Passwords doent mask Credentials Parameter Looks like the Credentials Binding variable, not being a build parameter, is simply not covered by the existing build options. This is more a new feature, unless you can show that actual build parameters (entries on the "Build with Parameters" form) are also affected. Change By: Daniel Beck (21/Nov/14 6:13 PM) Issue Type: Bug NewFeature Labels: credentials,jenkins,mask-passwordsplugin,security, 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-19582) GoogleCode browser URL must end with '/source/'
rsandell commented on JENKINS-19582 GoogleCode browser URL must end with /source/ throwing a hudson.model.Failure should according to the docs display a more user friendly error page, but when I try that in my own plugin it just displays the oops page with full stacktrace anyways. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
rsandell commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved According to the javadoc of FormValidation, hudson.model.Failure and hudson.model.Descriptor.FormException; throwing any of those should display a user friendly error page, perhaps tweaking those to be able to go back to the correct form state could at least approve things. Although when I try to throw a hudson.model.Failure I get the standard oops page instead of a "nicer" error page. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Sangeeta Narang reopened JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Description for Credential specified in Global Credentials is unique, for example, "Group1 P4 Creds". But when I go to select the credential from select credential Attribute drop down shows "Perforce Password Credential" and the description contents are not even there. I am using templates from enterprise jenkins. The Credential description shows fine as "Perforce Password Credential (Group1 P4 Creds)", if they are used from within the job. Change By: Sangeeta Narang (21/Nov/14 6:39 PM) Resolution: WontFix Status: Closed Reopened 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-19582) GoogleCode browser URL must end with '/source/'
Daniel Beck commented on JENKINS-19582 GoogleCode browser URL must end with /source/ rsandell Same behavior in core, the Failure thrown when you upload e.g. a PNG file to Plugin Manager also shows a stack trace. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
Joshua Kugler commented on JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. @alexanderlink: how long was your Gerrit server down? In our case, it was down for several hours, and finally the Gerrit trigger just gave up, or became hung/wedged. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-25305) Windows slave JVM crashes
Pandu Aji commented on JENKINS-25305 Windows slave JVM crashes I'm seeing the same issue. Do we have any workaround (setting change, etc)? Is this bug confirmed? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
Kelsey Prantis commented on JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. Confirming that for us as well it was down a few hours. I'd also like to add that this isn't 100% reproducible even for us. Sometimes the server is down and comes back up with no issues, other times we encounter the issue in this ticket - it appears to be intermittent. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
Jesse Glick commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved I wonder if it would work to send a 204 response to prevent the browser from rendering any page from configSubmit, so that the form with pending modifications remains open and available for amendment. (Combined with some other mechanism for displaying a popup warning to the user that the submission was rejected.) Not perfect—some form field changes might have actually been applied before Jenkins got to the erroneous one—but better than the current behavior. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-node-stalker-plugin] (JENKINS-23125) Node Stalker does not work with job in folders
Lance Johnston commented on JENKINS-23125 Node Stalker does not work with job in folders This was actually fixed with a pull request I submitted that was accepted a while back. It's in the 1.0.4 release, but that release is not available in the plugin center. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-25739) Wrong revision used for upstream integration
slav dok created JENKINS-25739 Wrong revision used for upstream integration Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 21/Nov/14 7:54 PM Description: The "Integrate Branch" action is selectable per run. Let's say I have two runs, #2 @57 and #1 @45. You can select a previous run, not necessarily the latest/@HEAD. If I select #1, and then click "Integrate Branch" action, the message that is displayed before "Integrate this build to upstream" button is clicked shows correct SVN revision of run #1 @45. However when the plugin operates, it does not merge from revision of #1 as selected. Instead, it merges to upstream from HEAD of branch. Here is my log. As you can see, I tried to integrate @45, as evident from message, however the plugin operated on @57: This will merge http://svn/branches/feature (rev.45) to trunk-build Last Failure Switching to the upstream (http://svn/trunk) U New Text Document.txt U. At revision 57 Merging http://svn/branches/feature (rev.57) to the upstream C New Text Document.txt U. Found conflict with the upstream. Reverting this failed merge Switching back to the branch (http://svn/branches/feature@57) U New Text Document.txt U. At revision 57 Conflict found. Please sync with the upstream to resolve this error. Completed If the plugin always integrates from @HEAD of branch, then the "Integrate Branch" action should be moved from per-run-level to job-level, and the message should be fixed Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 svnmerge plugin: 2.3 Project: Jenkins Priority: Major Reporter: slav dok 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Paul Allen commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Please can you take a screenshot. I don't use enterprise Jenkins and perhaps it displays things a little different. If you look at the Markdown page on GitHub (https://github.com/jenkinsci/p4-plugin) and scroll down to the Credentials section I have screen shots for normal Jenkins. You can see here there is an example of multiple credentials. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-restrictions-plugin] (JENKINS-25726) Add started by a user JobRestriction
Christopher Suarez commented on JENKINS-25726 Add started by a user JobRestriction I'm going to give it a shot, I've branched ownership plugin, it seemed to fit better there... 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Sangeeta Narang updated JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Change By: Sangeeta Narang (21/Nov/14 10:02 PM) Attachment: 2014-11-21_13-07-41.snagproj Attachment: 2014-11-21_13-08-33.snagproj Attachment: 2014-11-21_13-08-57.snagproj 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Sangeeta Narang updated JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Change By: Sangeeta Narang (21/Nov/14 10:06 PM) Attachment: 2014-11-21_13-07-41.jpg Attachment: 2014-11-21_13-08-33.jpg Attachment: 2014-11-21_13-08-57.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Sangeeta Narang commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Just uploaded the jpeg screenshots. Please ignore the snagproj files. So as you can see if I have two perforce credentials, I can not differentiate between them from UI. As number of credentials grow it all become painful to differentaite between them. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Steve Jansen commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart I believe I figured this out. After experiencing this problem on a CentOS 6.5 VM, I decided to start the Jenkins server interactively (eg., java -jar jenkins.war ... ) I saw a very curious warning: Nov 21, 2014 10:46:51 PM jenkins.diagnosis.HsErrPidList init WARNING: Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: /tmp/jna/jna4408307760862063272.tmp: /tmp/jna/jna4408307760862063272.tmp: failed to map segment from shared object: Operation not permitted This reminded me of a very similar problem on CentOS 6.5 with ruby-build that I documented @ https://github.com/sstephenson/ruby-build/issues/604#issuecomment-54310466 The cause seems to be when $TMPDIR is mounted as noexec. Just re-mount your temp dir and tmpfs as executable: $ mount /dev/mapper/vglocal20140828-root00 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,noexec,nosuid,nodev) /dev/sda1 on /boot type ext3 (rw) /dev/mapper/vglocal20140828-tmp00 on /tmp type ext4 (rw,noexec,nosuid,nodev) /dev/mapper/vglocal20140828-log00 on /var/log type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) I was able to resolve by removing the noexec option from /tmp and tmpfs and re-mounting both: $ cp /etc/fstab /tmp/~fstab $ sudo vi /etc/fstab $ diff /tmp/~fstab /etc/fstab 11c11 /dev/mapper/vglocal20140828-tmp00 /tmp ext4 defaults,nosuid,nodev,noexec 1 2 --- /dev/mapper/vglocal20140828-tmp00 /tmp ext4 defaults,nosuid,nodev 1 2 14c14 tmpfs /dev/shm tmpfs defaults,nosuid,nodev,noexec 0 0 --- tmpfs /dev/shm tmpfs defaults,nosuid,nodev 0 0 $ sudo mount -o remount /tmp $ sudo mount -o remount tmpfs $ mount /dev/mapper/vglocal20140828-root00 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) /dev/sda1 on /boot type ext3 (rw) /dev/mapper/vglocal20140828-tmp00 on /tmp type ext4 (rw,nosuid,nodev) /dev/mapper/vglocal20140828-log00 on /var/log type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Daniel Beck commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Steve Jansen: To clarify, your solution enables safeRestart with OpenJDK, or the JDK crash dump logging (which is what hserrpid is about)? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-node-stalker-plugin] (JENKINS-23125) Node Stalker does not work with job in folders
Daniel Beck commented on JENKINS-23125 Node Stalker does not work with job in folders 1.0.4 has not actually been released to the repository. Only a snapshot has been published: http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/job-node-stalker/1.0.4-SNAPSHOT/ https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24589) Build History - name and links overlap if build names are long
Daniel Beck commented on JENKINS-24589 Build History - name and links overlap if build names are long Some related discussion and suggestions at https://github.com/jenkinsci/jenkins/pull/1466 Please consider commenting how/why/when a proposed solution would (not) work well. (Please limit your comments to constructive criticism.) I'll try to ask tfennelly in IRC about a short-term solution suitable for 1.580.x. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
Daniel Beck commented on JENKINS-25487 Exception not verbose with m2release plugin DEBUG Executing: cmd.exe /X /C "E:\javadev\tools\maven\bin\mvn.bat -B -X -D maven.repo.local=F:\javadev\tools\maven\localrepository -P defaultprofile,env-test,env-test validate" INFO The system cannot find the path specified. Looks like one of the specified paths does not exist, or cmd.exe is not found because the Path variable doesn't contain its parent folder. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
Casey McGinty commented on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Please turn this into a configurable options. This breaks for any Gradle build running tests. The workaround should not be necessary as the check is not valid. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
Casey McGinty edited a comment on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Please turn this into a configurable options. This breaks for any Gradle build running tests. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
Casey McGinty edited a comment on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Please turn this check into a configuration option. This breaks for any Gradle build running tests. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
Casey McGinty edited a comment on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Please turn this check into a configuration option. This breaks any multi-project Gradle build running tests. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
