[JIRA] (JENKINS-44456) Provide a way to access a stage name from within the stage and its contents

3 views
Skip to first unread message

Robert.Rotaru@thehartford.com (JIRA)

unread,
Jun 6, 2018, 10:26:02 AM6/6/18
to jenkinsc...@googlegroups.com
Robert Rotaru commented on New Feature JENKINS-44456
 
Re: Provide a way to access a stage name from within the stage and its contents

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).

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

Robert.Rotaru@thehartford.com (JIRA)

unread,
Jun 6, 2018, 10:26:03 AM6/6/18
to jenkinsc...@googlegroups.com
Robert Rotaru edited a comment on New Feature JENKINS-44456
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).

jessie.ye@hootsuite.com (JIRA)

unread,
Nov 26, 2018, 8:59:03 PM11/26/18
to jenkinsc...@googlegroups.com

Is STAGE_NAME supported for parallel branches in scripted pipeline?

 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

fescobar.systems@gmail.com (JIRA)

unread,
Feb 21, 2020, 10:48:03 AM2/21/20
to jenkinsc...@googlegroups.com

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.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

fescobar.systems@gmail.com (JIRA)

unread,
Feb 21, 2020, 10:52:02 AM2/21/20
to jenkinsc...@googlegroups.com
Frank Escobar edited a comment on New Feature JENKINS-44456
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 .
Reply all
Reply to author
Forward
0 new messages