https://issues.jenkins-ci.org/browse/JENKINS-37985
Yep. All of our independent jobs really just do one mvn invoke each. They are smart in that they can be passed a git tag to build, or they will work against master; this is really nice because sometimes we just want to trigger, independently, a certain subphase / substage of the pipeline without going through all the steps. I think this will maintain durability of the pipeline as a whole, but also be flexible enough to meet our needs for maintaining the same basic behavior as we had before Jenkins had this advanced pipeline. Being able to see the launched job's console output will be valuable and make 'build' consistent with all the other types of launchers, well, the only one I know of, the 'sh' target. On Fri, Sep 2, 2016 at 7:30 AM, Baptiste Mathus <m...@batmat.net> wrote: > You should probably file an issue in Jira with this. > > IMO the potential big issue of this use case is that if the jobs you call > are big ones with many steps, you then make the durability durability > feature of pipeline far less useful. > > > Le 2 sept. 2016 7:08 AM, "jieryn" <jie...@gmail.com> a écrit : >> >> It would be nice if when a Pipeline invokes a Jenkins Job, that the >> log of that job would be visible inside the Blue Ocean pipeline output >> similar to the way any other pipeline stage works. We use individual >> jobs for each stage because it lets us get a lot of reusability for >> common functions which can be run independent of the pipeline. Right >> now, when each stage invokes a dedicated job, the pipeline has almost >> no information in it other than the stage/job status. It would be >> really useful to consume the launched job's console output.... >> >> -- >> 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/CAArU9ianBAXQAhbDxBMyqAzyUHG2EsebePkczZDPinrWwHuneA%40mail.gmail.com. >> 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/CANWgJS6BD550kS4pmb2KaTfuDxa6oqOSM-1hMfCzG8yja06o%2BA%40mail.gmail.com. > 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/CAArU9iZ9BQLcV6Om%2BZRSRkeEjWpjqp4K0CdknxeRjPYnapG96g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
