I have an imperative pipeline with the first stage being ‘build-proper.’ Once the entire job completes I see this:
[cid:image001.png@01D2AC57.D5D230E0] Which is nice. However for a job that is still in-progress I don’t see the Artifacts URL, even though I do see other information about the job. I can see that the Artifacts themselves actually are available at this time by manually entering something like: <Jenkins-URL>/job/<JOB>/53/artifact/ So it seems that all that is missing is the presentation of the ‘Build Artifacts’ URL itself. Is there any way to force this to happen earlier? Context: The build is sending mail once “unstable” is detected and then it is proceeding with down-stream operations such as functional testing. Unfortunately my users do not have easy access to see why the build was unstable. Seems that this is generally true for both Blue Ocean and Classic, but I am more interested in classic. From: Gardell, Steven Sent: Monday, March 13, 2017 7:30 AM To: jenkinsci-users@googlegroups.com Subject: RE: Future of 'pipeline' in the context of Blue Ocean? This is not my experience. I see two different bad behaviors: 1) The display presented for a currently running job is simply wrong, with the tool showing a running downstream serial activity that doesn’t exist. Once the overall job completes it “pops” back to a somewhat more correct presentation. See #2 2) Presentation of a build with multiple levels of parallelism (e.g. where one of the parallel activities is forked into parallel activities that re-join) does not present correctly Maybe there is some documentation lurking somewhere about structuring Scripted pipelines in a Blue Ocean friendly fashion? If the expectation is that this should all work, I will create Jira items for these behaviors. Then there is the “visualization” question related to postBuild… From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Bayer Sent: Sunday, March 12, 2017 10:29 PM To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> Subject: Re: Future of 'pipeline' in the context of Blue Ocean? The Blue Ocean visualization works equally well for any Pipeline, whether Scripted or Declarative. The Pipeline editor in Blue Ocean only works with Declarative, but that's the only difference. On Mar 12, 2017 17:19, "Gardell, Steven" <sgard...@sonusnet.com<mailto:sgard...@sonusnet.com>> wrote: Not surprisingly the Blue Ocean site is full of references to the “Jenkins Pipeline.” But it turns out that this really referring to the declarative pipeline. My experience is that in its current state Blue Ocean is a step back, or at best sideways, for the imperative/scripted pipeline. Following threads here and elsewhere it is pretty clear that the vernacular is converging to equate “Blue Ocean Pipeline” with “Declarative Pipeline.” My question is do we see the Blue Ocean UI more fully embracing the imperative pipeline in the future as might be inferred from the statement “The intention is that as Blue Ocean matures there will be less and less reasons for users to go back to the existing UI” or do we see the imperative pipeline going away? Or possibly some tweaks to how imperative pipelines are written to provide Blue Ocean with a better decoder ring? I ask because converting our imperative pipelines to declarative is looking rather non-trivial. Along a somewhat related vein, our imperative pipelines make use of the postBuild plugin to summarize various sorts of build results. But I don’t find any of that material presented in the Blue Ocean UI. So I gather it is not supported. Will it be? Or some other way of achieving the same end? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CY1PR0301MB1996CCE2CB0584FEC064A34EB8250%40CY1PR0301MB1996.namprd03.prod.outlook.com<https://groups.google.com/d/msgid/jenkinsci-users/CY1PR0301MB1996CCE2CB0584FEC064A34EB8250%40CY1PR0301MB1996.namprd03.prod.outlook.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOah319LAkXVaHLRJucoz%3DySb%2BYWRHO3UKEtAKf2H8uSPw%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOah319LAkXVaHLRJucoz%3DySb%2BYWRHO3UKEtAKf2H8uSPw%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CY1PR0301MB1996D4B906B0676A403E7307B8080%40CY1PR0301MB1996.namprd03.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
