[JIRA] (JENKINS-55115) shard / stage in pipeline test name cannot be disabled
Title: Message Title Simon Weber commented on JENKINS-55115 Re: shard / stage in pipeline test name cannot be disabled I don't think it's really related to the original issue - I don't even know if $class: XUnitPublisher is a supported interface - but for what it's worth I haven't seen issues once switching to the new xunit( syntax on the latest release. To get back on topic, I restored the old naming behavior by passing null instead of pipelineTestDetails here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-55115) shard / stage in pipeline test name cannot be disabled
Title: Message Title Simon Weber created an issue Jenkins / JENKINS-55115 shard / stage in pipeline test name cannot be disabled Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-12-10 21:53 Environment: jenkins 2.149 xunit plugin 2.31 junit plugin 1.26.1 Priority: Minor Reporter: Simon Weber Newer versions of the xdist plugin set pipeline information like parallel branch and stage into the test name itself (I believe as of https://issues.jenkins-ci.org/browse/JENKINS-45826). This is helpful in some cases, but can cause problems: upgrading from an older version breaks test history (since its name has changed) in situations where branch isn't relevant to the results (eg parallelizing a test suite with dynamically-named branches) it's difficult to visually group failing tests, since they're broken up by branch name So, I'd like to disable this behavior, but as far as I can tell it can't currently be done. Using step([$class: 'XUnitPublisher' instead of xunit([... is close, but also seems to cause race conditions such as: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at java.util.ArrayList$Itr.next(ArrayList.java:851) at hudson.tasks.junit.TestResult.tally(TestResult.java:705) at hudson.tasks.junit.TestResult.merge(TestResult.ja
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Simon Weber commented on JENKINS-53858 Re: Deadlock on EC2 resources I was able to recreate the problem pretty easily in staging, and master + https://github.com/jenkinsci/ec2-plugin/pull/321 has fixed it so far for me. I'm planning to roll it out in prod asap. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-41194) Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.
Title: Message Title Simon Weber commented on JENKINS-41194 Re: Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job. Here's a potential fix to try out: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/master...venmo:resolve_pipelines. ymmv; I mostly just copied the approach from https://issues.jenkins-ci.org/browse/JENKINS-38825. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Ok, here's the changes: https://github.com/jenkinsci/tikal-multijob-plugin/compare/master...venmo:pipeline-compat. Be sure to read it over before trying it out: there are a variety of things I didn't take the time to support since we don't use them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Alright, I've got things largely working. I'll clean things up and post some code tomorrow. I'll probably stop short of creating a PR, since my changes cut a lot of corners (eg removing some features around scm changes) in the interest of resolving the blocker. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs I made some progress on this today, mostly by switching from AbstractBuild/Project to Run/Job. I've got pipeline projects kicking off now, though there are problems propagating the result. I'll post back when I've got something workable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Maybe Sam Van Oort or Jesse Glick would be able to help (given their work on https://issues.jenkins-ci.org/browse/JENKINS-26050)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber edited a comment on JENKINS-38825 Re: MultiJob does not build Pipeline jobs I'm happy to work on this if someone can point me in the right direction.Notably, the trigger plugin seems to work fine on its own (see https://issues.jenkins-ci.org/browse/JENKINS-38998?focusedCommentId=280639&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280639); this problem seem's seems to be on multijob's end. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Simon Weber commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs I'm happy to work on this if someone can point me in the right direction. Notably, the trigger plugin seems to work fine on its own (see https://issues.jenkins-ci.org/browse/JENKINS-38998?focusedCommentId=280639&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280639); this problem seem's to be on multijob's end. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Simon Weber commented on JENKINS-38998 Re: Cannot trigger pipeline job Ok, I think the trigger plugin actually works as of 2.29; what I was describing was done in https://issues.jenkins-ci.org/browse/JENKINS-26050. I'm able to trigger a build both blocking and nonblocking builds of a pipeline, just not as part of a multijob phase. So, I think this can be closed, but https://issues.jenkins-ci.org/browse/JENKINS-38825 is still valid. My environment is trigger 2.32 and jenkins 2.34, in case it's relevant. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Simon Weber commented on JENKINS-38998 Re: Cannot trigger pipeline job Having read over https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#historical-background, I'm guessing all the references to AbstractProject/Build would need to be changed? It looks like an awful lot of code... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Simon Weber commented on JENKINS-38998 Re: Cannot trigger pipeline job This is a blocker for us as well. I'm happy to try and fix this if a maintainer can point me in the right direction. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Tony Bridges I don't think this was solved for us until I upgraded Jenkins. I'm not sure what combination of the jenkins, trigger plugin, and multijob plugin upgrades is necessary to solve it, but the environment I described earlier has been rock solid for months now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type We haven't seen this issue in a few months. We're now running Jenkins 1.628, trigger plugin 2.27, and multijob from source at https://github.com/jenkinsci/tikal-multijob-plugin/pull/65. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28184) Copy artifacts from all "Downstream build of"
Title: Message Title Simon Weber commented on JENKINS-28184 Re: Copy artifacts from all "Downstream build of" In case it helps, here's a script I've been using to work around this: https://gist.github.com/simon-weber/35f5d27a21ebf9b8ad8e. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type I just triggered an identical hang with the upgraded plugin, so it doesn't look like it's fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type So I've got my first example, but it's actually not for a multijob build! In this case, the parent build used https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin to trigger and block on the downstream build (which itself was a multijob build). The parent build was timed out after 20 minutes while the child was successful. So, perhaps the problem is actually with that plugin instead? My understanding is that it's a dependency of the multijob plugin. My installed version was 2.25 (I've since upgraded to 2.27 in case that fixes it). Here are the logs, but they're not too interesting: parent build: Waiting for the completion of platform_parallel Build timed out (after 20 minutes). Marking the build as aborted. Build was aborted child (multijob) build: [MultiJob] Starting job venmo_platform. [MultiJob] Starting job venmo_platform. [MultiJob] Starting job venmo_platform. [MultiJob][Debug] Create executor service. [MultiJob][Debug] Create task venmo_platform [MultiJob][Debug] Create task venmo_platform [MultiJob][Debug] Create task venmo_platform [MultiJob][Debug] Shutdown. [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] Timeoutexception, continue [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] future is started [MultiJob][Debug] future is started [MultiJob][Debug] future is started [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] future is started [MultiJob][Debug] Thy to start future for venmo_platform [MultiJob][Debug] future is started <"snip; this repeats for a long time"> [MultiJob][Debug] Result value is SUCCESS [MultiJob] Finished Build : #29045 - of Job : venmo_platform with status : SUCCESS [MultiJob][Debug] Finish execution of SUCCESS [MultiJob][Debug] Check phase termination. <"one of these for each subbuild"> [MultiJob][Debug] Continuation calculation. Finished: SUCCESS
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Sounds good. I'll update to that revision and hopefully have an example in the next few days. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Mathieu Cantin bummer; we just had a build hang. Here are the logs, my comments <"like this"> so jira highlights them. From the build itself: Started by upstream project "platform_deploy_listener" build number 219 <"snip"> [MultiJob] Starting job platform_parallel. [MultiJob] Starting job platform_parallel. [MultiJob] Starting job venmo_platform_external_integration. [MultiJob] Starting job venmo_platform_external_integration. [MultiJob] Starting job scope_frontend. [MultiJob] Finished Build : #96 - deploy of Job : scope_frontend with status : SUCCESS [MultiJob] Finished Build : #6837 of Job : platform_parallel with status : SUCCESS [MultiJob] Finished Build : #6836 of Job : platform_parallel with status : SUCCESS [MultiJob] Finished Build : #1248 - deploy of Job : venmo_platform_external_integration with status : SUCCESS Build timed out (after 20 minutes). Marking the build as aborted. [MultiJob] Aborting all subjobs. [MultiJob] Aborting platform_parallel. [MultiJob] Aborting platform_parallel. [MultiJob] Aborting venmo_platform_external_integration. [MultiJob] Aborting venmo_platform_external_integration. [MultiJob] Aborting scope_frontend. Build was aborted <"snip"> [MultiJob] Finished Build : #1247 - deploy of Job : venmo_platform_external_integration with status : ABORTED <"here's the build that hung"> From Jenkins: Jun 22, 2015 2:58:55 PM INFO venmo_platform_test_and_deploy - #863 Started by ... Jun 22, 2015 3:09:10 PM INFO hudson.model.Run execute venmo_platform_external_integration #1247 main build action completed: SUCCESS <"here we see it completed successfully"> Jun 22, 2015 3:09:11 PM INFO hudson.model.Run execute venmo_platform_external_integration #1248 main build action completed: SUCCESS Jun 22, 2015 3:09:20 PM SEVERE hudson.model.Executor finish1 Executor threw an exception java.util.NoSuchElementException <"perhaps this is related? We keep the most recent 1000 builds."> at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.subList(RunList.java:139) at hudson.tasks.LogRotator.perform(LogRotator.java:125) at hudson.model.Job.logRotate(Job.java:467) at hudson.model.Run.execute(Run.java:1808) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) <"these look to be expected"> Jun 22, 2015 3:18:48 PM INFO hudson.model.Run execute platform_deploy_listener #219 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:73) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:135) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$Abstrac
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Ok, I had to fix a few unrelated problems, haha. The hanging I was seeing before was caused by Jenkins taking a long time to discard old builds. I'm not sure why that was triggered by updating the plugin and restarting – maybe I just got unlucky? Anyway, after fixing all that other stuff and upgrading, things look good! I'll know for sure next week once we have some real load on it, but this looks promising =) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Whoops! I pasted the wrong thing. Let me do some debugging and get back to you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Mathieu Cantin, that fix didn't work for us: it made all builds hang. I found this error in the logs: Jun 19, 2015 9:34:03 PM WARNING hudson.triggers.Trigger checkTriggers org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for hudson.model.FreeStyleProject@b347b18[venmo_platform_auto_pr] java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:155) at hudson.triggers.Trigger.checkTriggers(Trigger.java:266) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 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:724) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28516) refspec is not applied on clone (initial fetch)
Title: Message Title Simon Weber commented on JENKINS-28516 Re: refspec is not applied on clone (initial fetch) This is particularly brutal when using "delete repository and force clone" with shallow clones. Is anyone planning to tackle this soon? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type @mcantin, I just installed your changes from source and unfortunately we're still seeing the problem. I've only seen hangs when one of the child builds failed, in case that's useful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28184) "Downstream build of" only selects most recent build
Simon Weber commented on JENKINS-28184 "Downstream build of" only selects most recent build Sorry, I was unclear. I'm referring to a situation in which the upstream build starts more than one of the same downstream build, all of which are linked by fingerprinting. From my understanding, you're referring to a situation in which the upstream only starts one downstream build (of which more than one have been triggered in the past). For example, imagine a situation in which you have one upstream build. It's purpose is to run tests in parallel. To do this, it just runs 2 downstream builds that each run half of the test suite. All of these are linked by fingerprinting on, say, the upstream's BUILD_TAG. The bug I'm reporting it that attempting to copy artifacts inside upstream for "downstream build of (upstream, $BUILD_NUMBER)", artifacts are only copied from the downstream build with the highest build number. In this situation, I'd expect artifacts to be copied from all downstream builds. Let me know if you need more detailed reproduction instructions – I can get them to you tomorrow. 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-28184) "Downstream build of" only selects most recent build
Simon Weber created JENKINS-28184 "Downstream build of" only selects most recent build Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 01/May/15 8:26 PM Description: The downstream build selector does not work with multiple downstream builds; only artifacts from the most recent downstream build are copied. Environment: Jenkins 1.593 copyartifact 1.35 Project: Jenkins Priority: Minor Reporter: Simon Weber 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Can we get some eyes on that pull request? We're still running into this issue daily. 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Here's a log message regarding the subjob that finished, but was still being waited on. My comments in [ square brackets ]: Apr 01, 2015 5:52:20 PM INFO hudson.model.Run execute platform_parallel #2620 main build action completed: SUCCESS [ this was the job the platform_pr was waiting on ] Apr 01, 2015 5:52:20 PM INFO hudson.model.Run execute platform_parallel #2619 main build action completed: SUCCESS Apr 01, 2015 5:52:20 PM WARNING jenkins.model.lazy.LazyBuildMixIn removeRun com.tikal.jenkins.plugins.multijob.MultiJobProject@4ff2acc8[platform_parallel] did not contain platform_parallel #1620 to begin with [ coincidence? was this supposed to be #2620? ] Apr 01, 2015 5:52:20 PM SEVERE hudson.model.Executor run Executor threw an exception java.util.NoSuchElementException at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.subList(RunList.java:137) at hudson.tasks.LogRotator.perform(LogRotator.java:124) at hudson.model.Job.logRotate(Job.java:449) at hudson.model.Run.execute(Run.java:1823) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type I finally got a thread dump! It looks like the problem is at this line: https://github.com/jenkinsci/tikal-multijob-plugin/blob/jenkins-multijob-plugin-1.16/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java#L216. Here's the relevant thread dump: "Executor #13 for qa-jenkins-psuedorunner-016 : executing platform_pr #2036" Id=257890 Group=main TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@385f18de at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@385f18de at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) at java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:389) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:216) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$DontRun.conditionalRun(BuildStepRunner.java:264) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1759) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Let me know if you need any other information from the dump – I saved it all just in 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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Is the api change you're thinking of in that specific version? We're still on version 1.593, and I think we saw this behavior on a version < 1.565.1 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] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type The logs aren't too informative. My comments are in [ square brackets ]. parent_job log Starting build job child_job. Starting build job child_job. Finished Build : #6631 of Job : child_job with status : SUCCESS Build timed out (after 20 minutes). Marking the build as aborted. [ this is from a plugin we use to timeout automatically ] Aborting all subjobs. Finished Build : #6630 of Job : child_job with status : ABORTED [ note that the parent job knows about the correct subjob since it knows which to abort ] Build was aborted Finished: ABORTED Jenkins log: Mar 12, 2015 2:34:40 PM INFO hudson.model.Run execute child_job #6631 main build action completed: SUCCESS Mar 12, 2015 2:34:45 PM INFO hudson.model.Run execute child_job #6630 main build action completed: SUCCESS [ this subjob did finish successfully and on time, but the parent job missed its result ] Mar 12, 2015 2:36:52 PM SEVERE hudson.model.Executor run [I don't think this is relevant - it happens later than the job finishes - but I figured I'd include it ] Executor threw an exception java.util.NoSuchElementException at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.subList(RunList.java:137) at hudson.tasks.LogRotator.perform(LogRotator.java:124) at hudson.model.Job.logRotate(Job.java:449) at hudson.model.Run.execute(Run.java:1823) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type > Sorry, I see the problem Oh, no worries; I could have done a better job describing the problem. > Do you have the "Execute concurrent builds if necessary" checked on child_job? Yes; on both child_job and parent_job. I had originally suspected this only happened when job numbers were interleaved due to another concurrent build, but that didn't happen in an example I just triggered now. I'll check the logs to see if there's anything interesting. 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber commented on JENKINS-27371 Parent builds sometimes hang on successful child builds of same type I'm not sure that has anything to do with the problem? The problem is that multijob will sometimes lose track of a child job and wait forever for its result. That forces us to abort the parent build (or else the parent job would run indefinitely). 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-27371) Parent builds sometimes hang on successful child builds of same type
Simon Weber created JENKINS-27371 Parent builds sometimes hang on successful child builds of same type Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 11/Mar/15 7:41 PM Description: With a job configuration like: parent_job: child_job child_job occasionally we'll get output that looks like this: Starting build job child_job. Starting build job child_job. Finished Build : #123 - Job : child_job with status : SUCCESS Aborting all subjobs. Finished Build : #124 - Job : child_job with status : ABORTED However, job #124 will always have finished successfully. We see this relatively rarely (~5% of parent_job builds?). My guess is that there's a race condition causing this, since we usually see this during times of high load (ie many child_job instances are being started). Environment: jenkins 1.593 multijob plugin 1.16 Project: Jenkins Priority: Major Reporter: Simon Weber 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] [github-plugin] (JENKINS-24291) GitHub plugin to make parameters from webhook data
Simon Weber commented on JENKINS-24291 GitHub plugin to make parameters from webhook data I'm running into a similar issue: I need access to the hook actor, but the plugin throws that information away. Specific parameters sound good - this is what https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin does - but we might also want to dump the entire hook to an environment variable. I could probably send a PR for this at some point. 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.
