[JIRA] (JENKINS-36087) Set stage result manually

1,184 views
Skip to first unread message

martin.stolle@iav.de (JIRA)

unread,
Jun 20, 2016, 9:41:01 AM6/20/16
to jenkinsc...@googlegroups.com
Martin Stolle created an issue
 
Jenkins / Improvement JENKINS-36087
Set stage result manually
Issue Type: Improvement Improvement
Assignee: Sam Van Oort
Components: pipeline-stage-view-plugin, workflow-plugin
Created: 2016/Jun/20 1:40 PM
Environment: Jenkins 2.9
Pipeline 2.1
Pipeline Stage View Plugin 1.4
Windows 7, 64bit
Labels: jenkins plugin pipeline stage
Priority: Minor Minor
Reporter: Martin Stolle

I would like to set the result of a stage.

{{
currentStage.result = 'SUCCESS'
currentStage.result = 'FAILURE'
currentStage.result = 'NOT_EXECUTED'
currentStage.result = 'ABORTED'
}}

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

svanoort@cloudbees.com (JIRA)

unread,
Jun 23, 2016, 12:24:08 PM6/23/16
to jenkinsc...@googlegroups.com
Sam Van Oort commented on Improvement JENKINS-36087
 
Re: Set stage result manually

Let's look at the desired result from a broader context: I what you're looking for here is really the ability to programmatically add additional information about stage execution (besides pass/fail) and display it in the UI. Does that sound about right?

The combination of https://issues.jenkins-ci.org/browse/JENKINS-26522 (annotated block status) and JENKINS-26107 (block-scoped stages, implemented in https://github.com/jenkinsci/pipeline-stage-step-plugin/pull/4) will give this result if a UI layer can be added on top of this (though it would require more complex analysis to generate this).

I am imagine syntax like: https://issues.jenkins-ci.org/browse/JENKINS-26522?focusedCommentId=253869&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-253869

Then add some basic rules to allow custom coloring of stages based on whether some annotation is present (attached to either start or end node, stage view analyses by then will be smart enough to do what needs to be done).

That approach fits with the execution model for pipelines - you can build up state as you go by attaching Actions to the nodes (which get carried to the overall block).

Tagging Jesse Glick to see if he agrees or has a better notion here.

martin.stolle@iav.de (JIRA)

unread,
Jun 24, 2016, 5:48:01 AM6/24/16
to jenkinsc...@googlegroups.com

Let's look at the desired result from a broader context: I what you're looking for here is really the ability to programmatically add additional information about stage execution (besides pass/fail) and display it in the UI. Does that sound about right?

That sounds right. The annotated block status is pretty similar to my ticket.

martin.stolle@iav.de (JIRA)

unread,
Jun 24, 2016, 5:50:02 AM6/24/16
to jenkinsc...@googlegroups.com
Martin Stolle updated an issue
Change By: Martin Stolle
I would like to set the result of a stage.

{ { code}
currentStage.result =  'SUCCESS'
currentStage.result =  'FAILURE'
currentStage.result =  'NOT_EXECUTED'
currentStage.result =  'ABORTED'
{code } }

svanoort@cloudbees.com (JIRA)

unread,
Jun 29, 2016, 12:30:01 PM6/29/16
to jenkinsc...@googlegroups.com
Sam Van Oort closed an issue as Fixed
Change By: Sam Van Oort
Status: Open Closed
Resolution: Fixed

svanoort@cloudbees.com (JIRA)

unread,
Jun 29, 2016, 12:30:01 PM6/29/16
to jenkinsc...@googlegroups.com

Martin Stolle I'm going to go ahead and close this one out as a duplicate of JENKINS-26522 but add a note that it needs a UI representation there which maps to stage view

ken.roland@arcticwolf.com (JIRA)

unread,
Jan 30, 2017, 9:04:02 AM1/30/17
to jenkinsc...@googlegroups.com

Sam Van Oort, you closed this as fixed instead of duplicate. Got me all excited for a minute

kamesh.raj@gmail.com (JIRA)

unread,
Apr 4, 2019, 5:21:02 PM4/4/19
to jenkinsc...@googlegroups.com

I don't see a fix or resolution for this issue? but the issue's status is Resolved, should this be open instead?

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages