-
New Feature
-
Resolution: Fixed
-
Major
-
None
Please provide a way to access the stage name from within the stage and its contents (like post).
Background
I have a multibranch declarative script. I am struggling with the limitation of one JenkinsFile per branch. I want to run various tasks (i.e. stages) on the branch (e.g. build several separate apps) and have a clear indication of which stage failed in the email notification subject sent on failure. I assume that stage processing will stop as soon as one stage fails. The post clause can then call the email-ext plugin and specify in Subject the stage that failed. Developers will then see quickly which task failed, rather than having to look through the console log (or email body).
- is duplicated by
-
JENKINS-40443 Possibility to know the current stage in a Pipeline
-
- Resolved
-
- is related to
-
-
- Open
-
- links to
[JENKINS-44456] Provide a way to access a stage name from within the stage and its contents
Zalan Meggyesi
added a comment - martin_haeusler According to Github, it's not in the currently released version of the plugin. I've opened an issue (JENKINS-45713) to ask about a new release, keep an eye on that.
Zalan Meggyesi
added a comment - martin_haeusler According to Github, it's not in the currently released version of the plugin. I've opened an issue ( JENKINS-45713 ) to ask about a new release, keep an eye on that. 
David Aldrich
added a comment - abayer Thanks for releasing this change. Where can I find out what the related env variable is, and perhaps an example of how to use it?
David Aldrich
added a comment - abayer Thanks for releasing this change. Where can I find out what the related env variable is, and perhaps an example of how to use it? Zalan Meggyesi
added a comment - abayer Many thanks, Andrew! This is SO very useful (I was about to implement a wrapper to the stage step which does exactly that) - thanks.
Mor L
added a comment - - edited This is SO very useful (I was about to implement a wrapper to the stage step which does exactly that) - thanks. The wiki still shows 2.2 as the latest release version, despite the README below also showing 2.3 as available (and archives also showing 2.3 as available).
https://wiki.jenkins.io/display/JENKINS/Pipeline+Stage+Step+Plugin
Is there a reason for this?
Robert Rotaru
added a comment - - edited The wiki still shows 2.2 as the latest release version, despite the README below also showing 2.3 as available (and archives also showing 2.3 as available).
https://wiki.jenkins.io/display/JENKINS/Pipeline+Stage+Step+Plugin
Is there a reason for this? 
Jessie Ye
added a comment - Is STAGE_NAME supported for parallel branches in scripted pipeline?
It would be better if we can get the current stage name and the RESULT. **On that way we can take decisions based on current stage result in the post conditions.
Kevin Burnett
added a comment - thanks for rocking this out. i was very excited that it was going to solve my use case, but i don't think it has yet. when I access STAGE_NAME from within the post block in my shared library, it's always yielding "Declarative: Post Actions," which is not what I need. I'd like to know if the build failed during the "commit" stage, "acceptance_tests", "deploy", etc. The person who answered this stackoverflow question seems to be having the same issue, and they worked around it by manually setting a variable for stage and then referencing their own variable. This is the sort of duplication I was hoping to avoid. does this use case deserve another jira issue?
Kevin Burnett
added a comment - thanks for rocking this out. i was very excited that it was going to solve my use case, but i don't think it has yet. when I access STAGE_NAME from within the post block in my shared library, it's always yielding "Declarative: Post Actions," which is not what I need. I'd like to know if the build failed during the "commit" stage, "acceptance_tests", "deploy", etc. The person who answered this stackoverflow question seems to be having the same issue, and they worked around it by manually setting a variable for stage and then referencing their own variable. This is the sort of duplication I was hoping to avoid. does this use case deserve another jira issue? 
How can we access this variable now in declarative pipelines? Is this functionality already published in Jenkins? It would be really useful to have this for sending notifications in case of build failures.