[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder commented on JENKINS-46715 Re: Error steps may change to show up as errors in pipeline view I have just seen that the same bug seems to pop up also in (one of my few) declarative pipelines: Besides not showing the failing stage in BO, it actually also manifests in stages with 0ms duration in the Stage View (see the three blue lightnings in the screenshot) Today's build (see the second build from top that is highlighted in yellow in the screenshot; mind it was just 2 hours ago) is still OK, but I assume/guess it will show up wrongly tomorrow The last/bottom one is also OK, because it actually failed due to a non-zero exit code in shell script (and not by calling "error" step): [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE => So I guess/claim this bug is somehow related to calling the "error" step explicitly in the pipeline; in my case this happens within a shared pipeline library, but in the example of issue description this was not the case 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
[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-11-13-10-19-20-710.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-46715
Re: Error steps may change to show up as errors in pipeline view
[~tscherler] Yesterday I provoked an artifical new/up-to-date reproducer (version information: Jenkins Core 2.147, Jenkins Blue Ocean Plugin 1.9.0) by adding an {{error}} step at around the same point in the pipeline stage and {color:#00875a}while it looked OK immediately (or maybe ~1h) afterwards{color}, {color:#de350b}this morning it is NOT anymore!{color} # Initially it is still OK: ## BO: !TK-Branch-am-selben-Tag.png|thumbnail! ## Classic "Steps" view: !TK-Branch-am-selben-Tag-ClassicUI.png|thumbnail! # Today it is broken: ## BO for pipeline: !TK-Branch-am-nächsten-Tag-BUG.png|thumbnail! ## BO when selecting broken stage in pipeline: !TK-Branch-am-nächsten-Tag-Stage-mit-Fehler-BUG.png|thumbnail!
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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: TK-Branch-am-selben-Tag-ClassicUI.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: TK-Branch-am-selben-Tag-ClassicUI.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder commented on JENKINS-46715 Re: Error steps may change to show up as errors in pipeline view Thorsten Scherler Yesterday I provoked an artifical reproducer by adding an error step at around the same point in the pipeline stage and while it looked OK immediately (or maybe ~1h) afterwards, this morning it is NOT anymore! Initially it is still OK: BO: Classic "Steps" view: Today it is broken: BO for pipeline: BO when selecting broken stage in 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: TK-Branch-am-nächsten-Tag-BUG.png Attachment: TK-Branch-am-nächsten-Tag-Stage-mit-Fehler-BUG.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: TK-Branch-am-selben-Tag.png Attachment: TK-Branch-am-selben-Tag-ClassicUI.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title
Reinhold Füreder commented on JENKINS-46715
Re: Error steps may change to show up as errors in pipeline view
Thorsten Scherler First of all thanks a lot in advance for taking care of this mysterious and disturbing problem The classic UI shows the error as expected:
Of course the build itself is red (but this is also the case in BO)
The console log contains the error step output at the very end:
...
> Task :migrateDb FAILEDFAILURE: Build failed with an exception.* What went wrong:
Execution failed for task ':migrateDb'.
> Process 'command 'php'' finished with non-zero exit value 1* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgBUILD FAILED in 14s
2 actionable tasks: 1 executed, 1 up-to-date
[Pipeline] echo
[DEBUG] gradlew phpunit exit code: 1
[Pipeline] pwd
[Pipeline] error
[Pipeline] }
$ docker stop --time=1 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965
$ docker rm -f 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] sh
[ACME-Pipeline-WS] Running shell script
+ docker stop d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
+ docker rm -f d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // ws
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] ansiColor
[Pipeline] {
[Pipeline] echo
Pipeline problem: PHPUnit DB integration test execution failed completely due to: "hudson.AbortException: PHPUnit DB integration test execution failed completely: Please check the previous step(s)" => Please check the "Console/Log Output" => Failure notification will be sent...
[Pipeline] }
[Pipeline] // ansiColor
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] echo
email-ext-recipients:
failingTestSuspects:
failingBuildSuspects:
developers: a.n...@acme.com
culprits: a.n...@acme.com
requester:
upstreamCommitters:
[Pipeline] emailext
Single culprit: [A Name]
Sending email to: a.n...@acme.com jenkins.ci...@acme.com
[Pipeline] stage
[Pipeline] { (kpi)
[Pipeline] echo
Listing all KPIs...
[Pipeline] echo[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/ACME-Pipeline
[Pipeline] {
[Pipeline] ws
Running in /var/lib/jenkins/workspace/ACME-Pipeline-WS-kpi
[Pipeline] {
[Pipeline] echo
Build Pipeline KPIs:
- Build duration: 2 minutes, 49.844 seconds ... time duration since build start
- Time duration since build scheduling: 2 minutes, 49.857 seconds
- Pipeline net execution time duration: 2 minutes, 42.368 seconds ... in "acme.build"
- Cycle time: 2 minutes, 50.570 seconds ... time duration since (oldest included production code) SVN commit (170953)
[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-10-30-12-32-53-068.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-10-30-12-30-10-803.png 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Thorsten Scherler commented on JENKINS-46715 Re: Error steps may change to show up as errors in pipeline view Reinhold Füreder to track down the root cause I would need to know what the classic UI is showing. I mean if the classic UI is showing the error but BO not then we know that it is specific to BO but if the classic UI shows the same problems then there is a general 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.
