This answers my sh issue: http://stackoverflow.com/questions/36956977/how-to-execute-a-command-in-a-jenkins-2-0-pipeline-job-and-then-return-the-stdou
Still would like to know how to exit a pipeline early. On Wednesday, May 25, 2016 at 10:11:44 AM UTC-7, Mark L wrote: > > I'm play with the pipeline sh directive and can't get it to behave how I > want it to. Maybe there's a workaround? > > The bash script I'm calling has two success modes with the following > semantics: (1) everything succeeded, now go onto the next (Jenkins) stage, > and (2) everything succeeded and the build done, so don't run any further > stages. > > How do I return two separate exit codes and not have the pipeline mark one > of them as failed (in red)? > How do I exit the pipeline early (not run all stages), and have the build > marked as successful? > > Thanks! > > > -- 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/09fba0c0-6827-4c33-91a7-cfb8d1a27545%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
