I do like Jenkins pipelines and the fact that now we can control Jenkins jobs via an inside repository file. I also love the looks of the upcoming Blue Ocean interface and I can't wait to see it as default interface.
Now, the reality is that there is a serious problem which seems to be ignored by the Jenkins development team: By implementing Jenkins pipelines you lose the ability to execute a build job outside jenkins. Due to this our current pipelines are mostly just one execution of 'make', so we can't really benefit from having the execution steps splitted and nicely-displayed by Jenkins. Like most users we do have multi-stage bash/make scripts that are building the product. Is there a way to implement Jenkins pipelines and still be able to run local builds? What is you take on this? -- 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/fd3b2419-9224-444b-9e16-76853b04cb25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
