[JIRA] (JENKINS-46170) Capability to add notes to stages (regardless of the actual result)
Title: Message Title Sam Van Oort assigned an issue to Unassigned Jenkins / JENKINS-46170 Capability to add notes to stages (regardless of the actual result) Change By: Sam Van Oort Assignee: Sam Van Oort 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling My suspicion is that one of the following is the cause based on the evidence above: 1. Unlikely: a very subtle change in the serialized format causes a net-new bug in JBoss Marshalling that prevents correct serialization. 2. Likely: Some subtlety in how readReplace methods are being handled (perhaps with regards to customizations in workflow or Groovy) – or especially with regards to order of operations here. This is supported by limited differences in the serialized output. 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling Oleg Nenashev I've attached a bunch of info from investigation above, but am running out of investigative ideas here aside from manually building and bisecting all the JBoss marshalling commits here, or tracing line-by-line through all the mutations of the SerialializableScript in the marshaller (I've done quite a bit of poking with the debugger & breakpoints here already). Would love to know if you have any ideas for how to attack this particular beast. 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling Writing up results of pair-investigation with Devin Nusbaum today and summarizing some previous findings 0. I'd previously established that the culprit here is a null "binding" field in the WorkflowScript when deserializing, and had not been able to determine how the setting of that field differs between JBoss Marshalling versions 1. This issue appears to occur with even very trivial Pipelines when trying to read the program.dat – see: https://github.com/svanoort/workflow-support-plugin/commit/60dff8f944407a46e70f1fcfc3843cf7da29d974#diff-5592588df61e52ede2b60dbc65f7009bR56 2. Some subtle differences in the serialization format between jboss-marshalling 1.4.12-jenkins-3 and 2.0.5.Final (I'd bisected the issue and confirmed it occurs as early as version 2.0.0 previously) – see attached program.dat files – but analyzing them briefly in a hex editor and via 'strings' does not show substantial differences. I.E. it's not like things simply aren't being serialized, the format is just modified to be a bit more efficient. 3. Stack traces when trying to read the SerializableScript are attached – note that the stacks seem more or less identical, aside froma switch for Java version changes, and different line numbers due to source changes in JBoss marshalling 4. Nothing obvious in the JBoss marshalling JIRA that would reflect this bug 5. Nothing obvious jumping out in the commits for JBoss marshalling that have changed https://github.com/jboss-remoting/jboss-marshalling/compare/1.4.12.Final...2.0.0.Final See data dumps: jboss-NEW-marshaller-unmarshal-thread.txt jboss-old-marshaller-unmarshal-thread.txt test-java8-LEGACY-marshaller-program.dat test-java8-new-marshaller-program.dat 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
[JIRA] (JENKINS-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-55174 NPE in build state marshalling Change By: Sam Van Oort Attachment: test-java8-LEGACY-marshaller-program.dat Attachment: test-java8-new-marshaller-program.dat 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-55174 NPE in build state marshalling Change By: Sam Van Oort Attachment: jboss-NEW-marshaller-unmarshal-thread.txt Attachment: jboss-old-marshaller-unmarshal-thread.txt 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-52011) workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams
Title: Message Title Sam Van Oort assigned an issue to Unassigned Jenkins / JENKINS-52011 workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams Change By: Sam Van Oort Assignee: Sam Van Oort 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort started work on JENKINS-55174 Change By: Sam Van Oort Status: Open In Progress 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling Oleg Nenashev Yup, that's the very same bugbear that's had me pulling out my hair for a while now. Right now I'm working on an alternate way of debugging it. 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-55174 NPE in build state marshalling Change By: Sam Van Oort Assignee: Sam Van Oort 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-52011) workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams
Title: Message Title Sam Van Oort stopped work on JENKINS-52011 Change By: Sam Van Oort Status: In Progress Open 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-52011) workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams
Title: Message Title Sam Van Oort updated JENKINS-52011 Jenkins / JENKINS-52011 workflow-cps: Illegal reflective access to java.io.ObjectStreamClass when cleaning up object streams Change By: Sam Van Oort Status: In Review Progress 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-36543) Boolean input parameter ignores default value of false
Title: Message Title Sam Van Oort commented on JENKINS-36543 Re: Boolean input parameter ignores default value of false Brandon Chew I'm quite confident we didn't revert this – are you absolutely sure this is happening with 2.9 or 2.10? Can you provide a case to reproduce? 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-41558) Memory leak in Jenkins stage view
Title: Message Title Sam Van Oort assigned an issue to Unassigned Jenkins / JENKINS-41558 Memory leak in Jenkins stage view Change By: Sam Van Oort Assignee: Vivek Pandey 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-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort commented on JENKINS-36914 Re: stash step is excessively slow on ARM Jesse Glick I'd agree we should burn agent CPU over master CPU, but do think it's worth saving some storage space on-master. The happy medium would be a high-performance algorithm such as LZ4, LZO, or LZF which gets most of the benefits of compression and can shrink highly-compressible content with a much lower CPU cost than Deflate (used by GZIP). I've seen very positive results with those algorithms in the past – they're fast enough that if you're transmitting fairly compressible content (ex JSON or XML payloads or source code) you can see time savings even in a data center with gigabit links. 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-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort commented on JENKINS-36914 Re: stash step is excessively slow on ARM Jesse Glick I know that the discrepancy vs. raw IO speeds is almost certainly due to GZIP compress/decompress. Using an uncompressed method might be beneficial in some cases (especially with poorly-compressible data). I'd have to benchmark the GZIP implementation on that specific platform and compare to the same one on a Intel/AMD laptop processor – but the benchmarks here show pretty large differences in performance between ARM and Intel processors: https://quixdb.github.io/squash-benchmark/ And if you're only using a single CPU thread to do decompression, with a pure-java implementation that is potentially less than optimal for the platform, then 0.7 MB/s seems not unreasonable for a compression rate. It's in the ballpark anyway - I'm seeing <10 MB compression rates reported for various quad-core+ ARM chips for native-code implementations of that compression algorithm, using multiple threads. Remember we're talking processors that only have a few watts to play with and fairly small cache sizes. 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-46074) Test flake in CpsFlowExecutionTest.quietDown
Title: Message Title Sam Van Oort closed an issue as Fixed I believe this one was resolved in my 1Q/2Q 2018 work to resolve persistence and order of operation issues. We can re-open if it recurs though. Jenkins / JENKINS-46074 Test flake in CpsFlowExecutionTest.quietDown Change By: Sam Van Oort Status: Open Closed Resolution: Fixed 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-47157) Jenkins pipeline hangs with "cannot start writing logs to a finished node"
Title: Message Title Sam Van Oort commented on JENKINS-47157 Re: Jenkins pipeline hangs with "cannot start writing logs to a finished node" Claas Diederichs Is this reproducible with the latest workflow-job version? We've just done a massive change to how logging is handled and I suspect this resolves it. 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-46076) Test flake in CpsThreadTest.stop
Title: Message Title Sam Van Oort closed an issue as Fixed I believe this one was resolved in my 1Q/2Q 2018 work to resolve persistence and order of operation issues. We can re-open if it recurs though. Jenkins / JENKINS-46076 Test flake in CpsThreadTest.stop Change By: Sam Van Oort Status: Open Closed Resolution: Fixed 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-46071) Test flake in WorkflowRunRestartTest.hardKill
Title: Message Title Sam Van Oort closed an issue as Fixed I believe this one was resolved in my 1Q/2Q 2018 work to resolve persistence and order of operation issues. We can re-open if it recurs though. Jenkins / JENKINS-46071 Test flake in WorkflowRunRestartTest.hardKill Change By: Sam Van Oort Status: Open Closed Resolution: Fixed 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-46077) Test flake in ParallelStepTest.suspend
Title: Message Title Sam Van Oort closed an issue as Fixed I believe this one was resolved in my 1Q/2Q 2018 work to resolve persistence and order of operation issues. We can re-open if it recurs though. Jenkins / JENKINS-46077 Test flake in ParallelStepTest.suspend Change By: Sam Van Oort Status: Open Closed Resolution: Fixed 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-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Sam Van Oort commented on JENKINS-54643 Re: A connection interruption causes the pipeline to fail when USE_WATCHING=true Jesse Glick Have you seen this one? 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-52907) Jenkins UI fails when restarting while builds are in queue or running
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-52907 Jenkins UI fails when restarting while builds are in queue or running Change By: Sam Van Oort Summary: Jenkins UI can be inaccessible if service is stopped fails when restarting while builds are in queue or running 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-53627) Getting java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun Exception while running Job
Title: Message Title Sam Van Oort closed an issue as Not A Defect Bidhan Saha This error occurs when one of the plugins you need is either not installed or failing to load – Jenkins should tell you which plugins are failing to load in the log when you restart. Update the Pipeline Job plugin from the update center and the issue will go away (that will automatically update dependencies). Jenkins / JENKINS-53627 Getting java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun Exception while running Job Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect 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-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort commented on JENKINS-36914 Re: stash step is excessively slow on ARM Bruce Merry Unfortunately I'm quite confident this is a result of the GZIP compression applied to stashes – the hardware itself probably does not have high performance for that algorithm. This operation thus becomes CPU-bound rather than network or I/O bound. I don't think we can really resolve this one since it's tied to the algorithm itself – using the latest compatible JDKs may help some. Jesse has suggested some workarounds as well. Finally, we may be able to switch out some of the GZIP implementations to higher-performance versions within the Jenkins core, but even so I doubt it'll yield great performance on ARM hardware. 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-36914) stash step is excessively slow on ARM
Title: Message Title Sam Van Oort closed an issue as Not A Defect Closing since the root cause here is that GZIP is demanding on ARM hardware Jenkins / JENKINS-36914 stash step is excessively slow on ARM Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect 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-31687) Which node Groovy code actually executes on is not documented clearly
Title: Message Title Sam Van Oort commented on JENKINS-31687 Re: Which node Groovy code actually executes on is not documented clearly Also documented here: https://jenkins.io/doc/book/pipeline/scaling-pipeline/ 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-31687) Which node Groovy code actually executes on is not documented clearly
Title: Message Title Sam Van Oort closed an issue as Done Mentioned in docs Jenkins / JENKINS-31687 Which node Groovy code actually executes on is not documented clearly Change By: Sam Van Oort Status: Open Closed Resolution: Done 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-52670) WorkflowGraph.FlowNodeContainer is causing memory performance issues
Title: Message Title Sam Van Oort commented on JENKINS-52670 Re: WorkflowGraph.FlowNodeContainer is causing memory performance issues Ayellet Lazar I see this one was released with the 5.5.2 beta on 2 Oct – could we mark this one as closed-released at this point? (Perhaps promoting the beta release to a full release along the way.) 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Sam Van Oort Labels: jep-210-regression regression 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Sam Van Oort commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults I have a fix for the logspam, but am still working on the testcase (a bit fiddly). 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Sam Van Oort commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Yes, this is purely a log-spam issue – we catch all exceptions from trying to store step arguments. Jesse's comment sparks some ideas for me. 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Sam Van Oort Assignee: Sam Van Oort 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Sam Van Oort Priority: Major Minor 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-42322) Docker rm/stop/... commands killed by the timeout, failing builds
Title: Message Title Sam Van Oort commented on JENKINS-42322 Re: Docker rm/stop/... commands killed by the timeout, failing builds Gustavo Chaves Which version of Docker itself are you using, and do you see the timeout error, or just the error "Failed to rm container" ? 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-54356) Make Pipeline placeholder tasks expose the same info as Freestyle builds do
Title: Message Title Sam Van Oort updated JENKINS-54356 Merged, pending release Jenkins / JENKINS-54356 Make Pipeline placeholder tasks expose the same info as Freestyle builds do Change By: Sam Van Oort Status: In Review Resolved Resolution: Fixed 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-54356) Make Pipeline placeholder tasks expose the same info as Freestyle builds do
Title: Message Title Sam Van Oort started work on JENKINS-54356 Change By: Sam Van Oort Status: Open In Progress 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-54356) Make Pipeline placeholder tasks expose the same info as Freestyle builds do
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-54356 Make Pipeline placeholder tasks expose the same info as Freestyle builds do Issue Type: Improvement Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2018-10-30 19:07 Labels: pipeline Priority: Minor Reporter: Sam Van Oort For Pipeline, we should expose the same info for our Placeholder tasks that occupy an executor as we do for normal Freestyle & other legacy build types. This allows the API to be used more effectively. Specifically, url, displayname, timestamp, etc Add Comment
[JIRA] (JENKINS-54356) Make Pipeline placeholder tasks expose the same info as Freestyle builds do
Title: Message Title Sam Van Oort updated JENKINS-54356 Jenkins / JENKINS-54356 Make Pipeline placeholder tasks expose the same info as Freestyle builds do Change By: Sam Van Oort Status: In Progress Review 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Sam Van Oort commented on JENKINS-37575 Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Kurt Routley Yes, 1.23, sorry, typo 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-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Sam Van Oort commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Vivek Pandey This one might be worth our team taking up, since locks are used rather heavily. 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-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-25858 java.io.IOException: Unexpected termination of the channel Change By: Sam Van Oort Assignee: Ivan Fernandez Calvo Sam Van Oort 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Patrick Ruckstuhl It sounds very plausible for me, though I'd have to double check the code responsible. 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-53888) Batch step running on a node other than the master fails
Title: Message Title Sam Van Oort commented on JENKINS-53888 Re: Batch step running on a node other than the master fails Éric Louvard Bhushan Shah Do you also have problems with Linux build agents as well? And do you see the same message in your logs as in the originally reported description? I don't think this relates to the recent Pipeline regression, though it could be related in some obscure way to the Controller.watch APIs added by Jesse Glick 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort closed an issue as Fixed Mitch McLaughlin I can guarantee this particular deadlock is resolved. If you're seeing a new deadlock, please open a ticket and include the thread dump in it. Thanks Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: Reopened Closed Resolution: Fixed 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-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Sam Van Oort commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Jose Blas Camacho Taboada Could you please provide some details? There should not be a race condition possible (if so, that's a bugfix we need to do). It sounds like you have what you need to fix that, from what you're saying. Thanks! 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-53425) Groovy.lang.MissingPropertyException: No such property: timestamps for class: groovy.lang.Binding
Title: Message Title Sam Van Oort updated JENKINS-53425 Jenkins / JENKINS-53425 Groovy.lang.MissingPropertyException: No such property: timestamps for class: groovy.lang.Binding Change By: Sam Van Oort Status: Fixed but Unreleased Resolved Released As: 1.46 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jesse Glick I'm working up a Hydra case for this – I think I have a pretty good idea why it didn't get reproduced before (log streaming from shell steps wasn't running for long enough in parallel, I believe). 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-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-53775 FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Change By: Sam Van Oort Assignee: Jose Blas Camacho Taboada 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-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Sam Van Oort commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Jose Blas Camacho Taboada Could I persuade you to please take a look at this? It looks like it should be a synchronization bug around pickle loading. I'm not actually as concerned with JobDSL + Pipeline because that's kind of an edge case situation, but I strongly suspect that a threading issue here will be causing other failures that people just don't know the cause of. Thanks! 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Thanks Lars Bilke – digging in, it seems this has pointed to the problem: we have a bug here with the log indexing, which for parallel steps it is showing parallels running shell steps is switching from one branch to another with just a few bytes of log at a time. My suspicion for Jesse Glick is that we have a combination of the Controller.watch API (which sends logs from a shell step in 100 ms slices) plus the indexing which is trying to index with each of these mini-slices of log. The crude solution would be to set up so we're sending logs from the Shell/Batch/Powershell steps less frequently (say, every 5s or so). This would greatly reduce the interleaving. For controller.watch without the log handling rewrite, this probably wasn't as much of an issue because the log data came in larger batches. We could also consider trying to buffer and consolidate those writes (at either end) but I suspect that will be considerably more complex to do correctly. 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jon B Yes, we can understand the potential security concerns (though they're less than with overall build). With those concerns in mind, you can email the thread dump in private to Jesse and I (svano...@cloudbees.com and jgl...@cloudbees.com). We'd appreciate any other information you can supply (the workflow subfolder of the build above, Pipeline scripts, etc). Thanks! 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jon B Lars Bilke kutzi We've pulled this from the update center, but still would badly like to solve this bug. In order to try to resolve this, we're asking if you could supply as much information as you feel comfortable about the builds that were running at the time the problem manifested. Specifically, if there's any way you could be persuaded to upload a ZIP / tar.gz of the build folder for those builds (appropriately censored), it would be extremely helpful. Especially helpful: the Pipeline and Shared Library code run, the 'workflow' subdirectory (contains XML files describing the build's step structure), the log file for the builds, and the log-index file for the build (both inside the build directory). 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps CC Daniel Beck – the PR to pull this from the update center is https://github.com/jenkins-infra/update-center2/pull/247 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-50960) Pipeline jobs hangs after restart with build trigger step
Title: Message Title Sam Van Oort commented on JENKINS-50960 Re: Pipeline jobs hangs after restart with build trigger step Lucie Votypkova Is this still reproducible? 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Sam Van Oort Priority: Major Blocker 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps kutzi One question: how many FlowNodes are in your build here? Not clear exactly where the bottleneck is here, but a few observations for Jesse Glick There seems to be a lot of remoting-related activity running, both de/serialization and crypto The monitoring thread for free disk space is blocking 4 other threads, locking on the ConsoleHandler We have 5 separate threads trying to do FileLogStorage operations (two blocked by others) These come up in stack traces for those: at org.jenkinsci.plugins.workflow.log.FileLogStorage$IndexOutputStream.write(FileLogStorage.java:163) at org.jenkinsci.plugins.workflow.log.FileLogStorage$IndexOutputStream.write(FileLogStorage.java:161) 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-43556) Stage View shows incorrect build result
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-43556 Stage View shows incorrect build result Change By: Sam Van Oort Priority: Major Minor 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-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort updated JENKINS-54032 released Jenkins / JENKINS-54032 ArgumentsActionImpl should protect against storing bizarre step arguments Change By: Sam Van Oort Status: In Review Closed Resolution: Done Released As: workflow-cps 2.59 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-37224) Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37224 Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT Change By: Sam Van Oort Issue Type: Improvement Bug 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Sam Van Oort edited a comment on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished [~jglick] Could you please take a look? Appears that the latest comment may reflect a regression due to controller.watch API. Edit: though it's not entirely clear from context 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Sam Van Oort commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished Jesse Glick Could you please take a look? Appears that the latest comment may reflect a regression due to controller.watch API. 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-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Sam Van Oort commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Jakub Pawlinski It is on the roadmap and has a couple engineers working hard on it (myself included), although we're not quite ready to demo or announce something (a few more pieces need to fall into place). 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I tried to reproduce this in my special-sauce loadtesting environment for Pipeline with lots of parallels (up to 100), and with parallels that do a lot of logging. For future reference (and my own records), testing was done with testcases MassivelyParallelNodes, ParallelsPlusSteps, ParallelsPlusStepsRealisticSlowed, and continuous-looping run of DeclarativeParallels (1 concurrent build). Looks like we're really going to need more detail to ID the problem here – a thread dump while load is high, and preferably a simple Pipeline that will reproduce the issue. 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-53901) Using readFile does not handle UTF-8 with BOM files
Title: Message Title Sam Van Oort closed an issue as Not A Defect This is due to a known problem with Java's implementation of the UTF-8 spec. Suggested an easy workaround in Pipeline code to solve the issue. Jenkins / JENKINS-53901 Using readFile does not handle UTF-8 with BOM files Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect 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-53901) Using readFile does not handle UTF-8 with BOM files
Title: Message Title
Sam Van Oort commented on JENKINS-53901
Re: Using readFile does not handle UTF-8 with BOM files
Jakub Pawlinski This is a known with the Unicode spec and the Java platform implementation of it, not Pipeline. In UTF-8 the BOM is neither needed nor suggested - since the BOM is essentially meaningless in UTF-8, Java transparently passes the BOM through. First I'd make sure to add the "encloding: 'UTF-8'" argument to your readFile step to ensure it reads as UTF-8. Then we do postprocessing to correct for nonstandard input. Some suggested solutions are available on StackOverflow. Personally, I'd do something like this to sanitize your input:
/** These are UTF-8 BOM characters */
private static String removeUTF8BOM(String s) {
return s.replace("\uEFBBBF", "");
}
(might need to be \u FEFF, try it both ways). There's also code snippets out there that do a more efficient approach, which only considers the leading bytes of the String.
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-54073) Jenkins Master Host CPU pegs to ~100% during parallel jobs
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: Jenkins Master Host CPU pegs to ~100% during parallel jobs Jon B Please attach a thread dump so that we can see what is happening while the CPU is running hot. Thanks! 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-53956) Pipeline job hangs forever at end
Title: Message Title Sam Van Oort commented on JENKINS-53956 Re: Pipeline job hangs forever at end Jose Blas Camacho Taboada Please could you take a look? Thanks! 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-53958) Pipeline Jobs not started when locale master Node is offline
Title: Message Title Sam Van Oort commented on JENKINS-53958 Re: Pipeline Jobs not started when locale master Node is offline Daniel Hoerner Not clear what you mean, what do you mean by "defined another master node" and "alternative master"? Specifically what does this mean: > I have defined another master Node with Name 'master' and this Node is online. 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-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Sam Van Oort commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history Tony Hoyle Marcus Philip You guys are welcome to take a stab at the proper fix for this if you like – the blocker with https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/55 is that it is simply reverting https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/35 – which makes sense with wider screens now quite common. What needs to happen is the graphs need to be at the top until the screen is wide enough, and then they should reflow to the right – but I'm no expert at CSS and our layouts aren't trivial, so I'm not sure how to do that. If someone else can provide a solution for that goal, I'd be happy to merge and release it though. 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-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort commented on JENKINS-54032 Re: ArgumentsActionImpl should protect against storing bizarre step arguments implemented 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-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort updated JENKINS-54032 Jenkins / JENKINS-54032 ArgumentsActionImpl should protect against storing bizarre step arguments Change By: Sam Van Oort Status: In Progress Review 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-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort started work on JENKINS-54032 Change By: Sam Van Oort Status: Open In Progress 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-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-54032 ArgumentsActionImpl should protect against storing bizarre step arguments Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-10-11 22:14 Labels: pipeline Priority: Minor Reporter: Sam Van Oort If a step takes objects as input arguments, these objects are is stored in an ArgumentsAction for visualization and to provide a record of parameters – unless the input fails to serialize. However Steps can take completely arbitrary input types. For robustness it would be better if we only store simple types that can be used for visualization (basically anything that is legal for a DescribableModel) and NOT just any random input. We also need to ensure complex objects passed in are sanitized (remove inputs containing passwords) & length-limited. If they're Describables we should explode them into UninstantiatedDescribables for recursive argument processing and safer storage. Concrete example: we've seen at least one example recently where Artifactory plugin's steps are passing in a class with the Pipeline-internal CpsScript as a (transient) field. This causes a serious memory leak because the Step's arguments can remain in memory after the build has completed and that CpsScript carries a lot of baggage. This isn't a bug in Pipeline itself per se – because plugins providing Steps shouldn't be abusing the inputs or passing in very complex object types – but it's better to protect against bad inputs than not to.
[JIRA] (JENKINS-53857) No option to disable build continuation when computer forcefully restarted
Title: Message Title Sam Van Oort commented on JENKINS-53857 Re: No option to disable build continuation when computer forcefully restarted Marley Kudiabor This was fixed via updates to the Pipeline plugin suite, but you'll need to be on a more modern core (2.62 IIRC) to consume the updates. 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-53857) No option to disable build continuation when computer forcefully restarted
Title: Message Title Sam Van Oort closed an issue as Duplicate Jenkins / JENKINS-53857 No option to disable build continuation when computer forcefully restarted Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate 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-53857) No option to disable build continuation when computer forcefully restarted
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-53857 No option to disable build continuation when computer forcefully restarted Change By: Sam Van Oort Priority: Blocker Major 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-44958) File handle leaks in *.log after hard kill
Title: Message Title Sam Van Oort commented on JENKINS-44958 Re: File handle leaks in *.log after hard kill Rick Liu Since Jesse forgot to communicate the key info: there's a huge change to logging that's just gone into beta release (available via the Experimental Update Center – see https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ ) that completely removes these extra log files. I'd argue that qualifies as Resolution: Fixed rather than "Won't Fix" but ::shrug:: 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-51824) Investigate Script Security compatibility with Java 10
Title: Message Title Sam Van Oort commented on JENKINS-51824 Re: Investigate Script Security compatibility with Java 10 No, we still need to double-check this after the groovy bump I think. But it's pretty fast. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Brian J Murrell Unfortunately, that and the proposed mitigation in https://issues.jenkins-ci.org/browse/JENKINS-53889 are all we've got as viable short-term solutions. It's not a matter of "polluting state" - the data Pipeline needs to figure out which of the stages set the UNSTABLE status simply isn't there, and injecting that into the current system will probably break it completely. Several other engineers and I are working on a comprehensive solution to the things that make this problem hard to solve. We've already had several top Jenkins engineers spend literally months going in circles working on find a solid implementation that solves this specific issue without causing major regressions – the pull requests are out there if you're curious. Unless someone comes up with an unexpectedly clever solution, what's left is waiting for that larger effort to wrap up and then this specific problem will be solved along the way. And that sucks, and we know it's frustrating waiting, but we're doing the best we can to get that to the point of an alpha release. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Brian J Murrell currentBuild.currentResult would be entirely unchanged. It has no representation within the Pipeline data model (it directly modifies the build). What this would do is ensure that no stages show up as "unstable" for you. Which gives you what you are asking for. If you want the ability to keep the UNSTABLE status and figure out which stage actually set it... well, see above, that's way more work than one would reasonably expect (and much riskier too). Plus it requires reworking steps that can generate that status (generally steps that process unit test results, so JUnit and others). 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-53889) Support post conditions that accept a range of stage statuses
Title: Message Title Sam Van Oort commented on JENKINS-53889 Re: Support post conditions that accept a range of stage statuses Andrew Bayer That would work - probably unstableOrBetter, and failureOrWorse would do the trick for 95% of users. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Denis Zakharov Brian J Murrell I've opened JENKINS-53889 which I think would resolve your biggest issue here by making it easy to catch and handle UNSTABLE statuses in declarative. 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-53889) Support post conditions that accept a range of stage statuses
Title: Message Title Sam Van Oort commented on JENKINS-53889 Re: Support post conditions that accept a range of stage statuses The worst aspects of the unstable status handling are resolved by this. 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-53889) Support post conditions that accept a range of stage statuses
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-53889 Support post conditions that accept a range of stage statuses Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-10-03 15:59 Labels: usability Priority: Major Reporter: Sam Van Oort For users of declarative pipeline, there are problems with coding 'post' conditions to handle stages that might come up as UNSTABLE rather than SUCCESS if a test fails. This means if a stage is unstable, then the 'success' condition will break. See example: https://issues.jenkins.io/browse/JENKINS-39203?focusedCommentId=350537=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-350537 Solving this requires writing separate post conditions for each possible status. Instead, it would be very good to support a 'statusGreaterThanOrEqual' condition that takes a Result code and runs if it's better than it (and perhaps statusLessThan, etc). Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Brian J Murrell [~zaharovdi] Short term, what we can do is roll back the support for UNSTABLE status. That means you never have to worry about this "bug" because we don't try to signal that a stage somewhere set that status – we simply go back to ignoring it entirely. What do you think? In the longer-term, we're building a new Pipeline engine that will replace CPS and provide solutions to a lot of painful issues (sandboxing, lack of an integrated debugger, stability and resource-use problems) and we're planning to address the way we store Step statuses there so that this ceases to be a problem. However I can't give you a firm timeline for that yet. For those who will ask "Why isn't this super easy? Why can't it be done tomorrow?!" – the answer is: "There's nothing actually storing when we set unstable status. And storing that is deceptively complex because statuses can interact and carries a huge risk of regressions." In fact, all the statuses besides success and failure are computed based on a pretty complex and delicate process. Much, much, much more is happening under the surface than users will actually see. Andrew Bayer Would it be viable to add a custom "UNSTABLE OR HIGHER" post condition for the Declarative post conditions? I think that would resolve the part of this that seems to be serious (breaking post behaviors that expect success only). 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-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Sam Van Oort commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Nico Schmoigl I'm glad to see you haven't had a recurrence. That sounds like you were held up due to I/O issues – only one operation can try to load a build from disk at a time, and if that takes a while and other operations are depending on that build being loaded they will be blocked until it finishes loading. We did some improvements over the last few releases of workflow-cps and workflow-job to support lazy-loading of the FlowExecution which can make these cases significantly faster (especially where we are using the Performance-Optimized durability mode). Looking at performance-plugin, it seems that the Performance plugin causes this due to trying to load all builds for each run (which is bound to create a bottleneck for other things trying to access the builds as well). Now, what I'd love to see is the full stack trace for that "endless loop" – it's possible in some rare cases if the build onLoad ends up invoking itself either directly or indirectly, but suggests a critical bug somewhere (perhaps Performance Plugin, perhaps a combination of plugins). Also, what is "YAD plugin" short for? "Yet Another Docker plugin"? If so, I'm very curious how that could be related because the timeout there applies to communications with the Docker server. 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Sam Van Oort commented on JENKINS-50993 Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Apurv Raj Have you tried the Stage View 2.10 upgrade? This looks like it may be a URL generation quirk somehow triggered by something the Splunk Plugin does – the 2.10 update includes at least some fixes to URL generation logic in Stage View. 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-53710) Update site signature validation fails on Java 11
Title: Message Title Sam Van Oort updated JENKINS-53710 Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Change By: Sam Van Oort Status: In Progress Review 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-52023) If we update Groovy to 2.4.12 for Java 10, Pipeline builds leaks Metaspace memory
Title: Message Title Sam Van Oort resolved as Cannot Reproduce It seems I can no longer reproduce the leaks – at least with current Java core versions – despite extensive testing. Something in the current round of hacking seems to have resolved this. Jenkins / JENKINS-52023 If we update Groovy to 2.4.12 for Java 10, Pipeline builds leaks Metaspace memory Change By: Sam Van Oort Status: Open Resolved Resolution: Cannot Reproduce 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-52024) Can't compile/test under Java 10 with mvn
Title: Message Title Sam Van Oort commented on JENKINS-52024 Re: Can't compile/test under Java 10 with mvn Oleg Nenashev I swear I had this working after the PRs attached... 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-46170) Capability to add notes to stages (regardless of the actual result)
Title: Message Title
Sam Van Oort edited a comment on JENKINS-46170
Re: Capability to add notes to stages (regardless of the actual result)
Specific ask from [~vgaidarji] and is to have a 'label' argument for shell step that does something like this:sh label:'clear home', script:'rm -rf $WORKSPACE/*' This will attach a custom 'MarkerAction' or something (I think NOT a LabelAction because that may have structural implications) - this is used for getDisplayName or whatever and replaces ArgumentActionAlternately, something working similarly that does it to general steps in a block like this:marker('stuff') { echo 'thing' sh 'do stuff'}But this doesn't replace display name necessarily, it may show other stuff.Impl note: Blue Ocean's rendering, maybe not just getDisplayName.UX: thought, include more than one field
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-46170) Capability to add notes to stages (regardless of the actual result)
Title: Message Title
Sam Van Oort commented on JENKINS-46170
Re: Capability to add notes to stages (regardless of the actual result)
Specific ask from Veaceslav Gaidarji and is to have a 'label' argument for shell step that does something like this: sh label:'clear home', script:'rm -rf $WORKSPACE/*' This will attach a custom 'MarkerAction' or something (I think NOT a LabelAction because that may have structural implications) - this is used for getDisplayName or whatever and replaces ArgumentAction Alternately, something working similarly that does it to general steps in a block like this: marker('stuff') { echo 'thing' sh 'do stuff' } But this doesn't replace display name necessarily, it may show other stuff.
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-26522) Annotated block/stage status
Title: Message Title Sam Van Oort closed an issue as Incomplete Jenkins / JENKINS-26522 Annotated block/stage status Change By: Sam Van Oort Status: Reopened Closed Resolution: Incomplete 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-26522) Annotated block/stage status
Title: Message Title Sam Van Oort reopened an issue Jenkins / JENKINS-26522 Annotated block/stage status Change By: Sam Van Oort Resolution: Incomplete Status: Closed Reopened Assignee: James Dumay 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-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Sam Van Oort commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Nico Schmoigl Ack, we'll wait untuil you have a chance to grab the thread dump – otherwise it'll depend on if this gets fixed by another bugfix. 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-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Sam Van Oort commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Nico Schmoigl Please could you attach a thread dump from Jenkins? 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Sam Van Oort commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Mike Kozell That specific case sounds a lot like a gremlin we've been chasing on and off for quite a while. I'm assigning this to Jose Blas Camacho Taboada to investigate. I think what you report may be independent of what was discussed here though which is probably the root cause of the issue: https://issues.jenkins-ci.org/browse/JENKINS-34256?focusedCommentId=336282=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-336282 through https://issues.jenkins-ci.org/browse/JENKINS-34256?focusedCommentId=332080=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332080 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-26148) Incorrect implementation of RetryStepExecution.stop
Title: Message Title Sam Van Oort updated JENKINS-26148 Jesse Glick I think we got all the parts released here, right? Jenkins / JENKINS-26148 Incorrect implementation of RetryStepExecution.stop Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException Change By: Sam Van Oort Assignee: Sam Van Oort Jose Blas Camacho Taboada 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.
