Step([$class: 'Mailer', recipients: the shell step fails, the Pipeline build’s status will be set to failed, so that the subsequent mail step will see that this build is failed. It is also useful when using certain post-build actions (notifiers) originally defined for freestyle projects which pay attention to the result of the ongoing build. Otherwise, consider using plain try- catch(- finally) blocks. ![]() This step is most useful when used in Declarative Pipeline or with the options to set the stage result or ignore build interruptions. The behavior of the step when an exception is thrown can be configured to print a message, set a build result other than failure, change the stage result, or ignore certain kinds of exceptions that are used to interrupt the build. If the body throws an exception, mark the build as a failure, but nonetheless continue to execute the Pipeline from the statement following the catchError step. withContext: Use contextual object from internal APIs within a block.unarchive: Copy archived artifacts into the workspace.getContext: Get contextual object from internal APIs.warnError: Catch error and set build and stage result to unstable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |