Timeline for Cleanest way to prematurely exit a Jenkins Pipeline job as a success?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2020 at 23:02 | answer | added | kgriffs | timeline score: 13 | |
| May 7, 2020 at 0:55 | answer | added | Katrina Brock | timeline score: 4 | |
| Oct 23, 2019 at 17:08 | answer | added | Ben Amos | timeline score: 26 | |
| Jul 10, 2018 at 11:29 | answer | added | CSchulz | timeline score: 23 | |
| Apr 16, 2017 at 23:35 | vote | accept | Alex | ||
| Apr 14, 2017 at 21:30 | answer | added | MrMesees | timeline score: 1 | |
| Apr 13, 2017 at 17:36 | answer | added | Alex | timeline score: 97 | |
| Apr 13, 2017 at 16:12 | comment | added | Alex | @Aurora0001 Nope, there's multiple stages left; this comes almost first thing in a 7 step job. | |
| Apr 13, 2017 at 16:11 | comment | added | Aurora0001 |
Could you not flip the logic around and if ($VALUE1 != $VALUE2) { /* rest of job */ } ? This should implicitly end the job (because there is no more code) if they are equal.
|
|
| Apr 13, 2017 at 16:04 | comment | added | Tensibai |
In groovy I'd just try a return 0, all in all any end of the groovy code which doesn't throw an exception should do I think. I'll let someone with more background on jenkins 2 confirm or infirm
|
|
| Apr 13, 2017 at 15:36 | comment | added | Alex | This isn't within a bash script, this is the pipeline job itself, so Groovy. Does that change things? | |
| Apr 13, 2017 at 15:36 | comment | added | Tensibai | Well, just bash scripts, exit 0 means success, exit non zero means failure... | |
| Apr 13, 2017 at 15:35 | comment | added | Alex | I thought that marked the job a failure? If I'm wrong and you can show documentation, I'd be happy to accept that as an answer | |
| Apr 13, 2017 at 15:33 | comment | added | Tensibai |
Just exit 0...
|
|
| Apr 13, 2017 at 15:31 | history | asked | Alex | CC BY-SA 3.0 |