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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CY1PR0301MB1996CCE2CB0584FEC064A34EB8250%40CY1PR0301MB1996.namprd03.prod.outlook.com. For more options, visit https://groups.google.com/d/optout.
