• Type: Story
• Resolution: Fixed
• Priority: Critical
• Component/s: blueocean-plugin
• Labels:

  • api

[JENKINS-38491] Add new "waitingForInput" status to API for runs, dag and steps

James Dumay created issue - 2016-09-26 03:30

James Dumay made changes - 2016-09-26 03:30

Epic Link

New: JENKINS-38490 [ 174672 ]

James Dumay made changes - 2016-09-26 03:30

Rank

New: Ranked higher

James Dumay made changes - 2016-09-26 03:32

Sprint

New: 26-september [ 101 ]

James Dumay made changes - 2016-09-26 03:32

Rank

New: Ranked higher

Collapse comment: Michael Neale added a comment - 2016-09-26 03:32, Edited by Michael Neale - 2016-09-26 03:37

Michael Neale added a comment - 2016-09-26 03:32 - edited

There is some api design thinking required - this could be part of the graph of things returned for the stage graph (I imagine this is how the stage view works), but we also want to be able to show on the main dashboard (which is new).

So this may be 2 parts: one is in the stage graph data, the other would be part of the overall job status so that it can show up as favourites (just thinking aloud...)

jamesdumay so is the data returned indicating the fields required out of scope of this? or in scope? not clear

Expand comment: Michael Neale added a comment - 2016-09-26 03:32, Edited by Michael Neale - 2016-09-26 03:37

Michael Neale added a comment - 2016-09-26 03:32 - edited There is some api design thinking required - this could be part of the graph of things returned for the stage graph (I imagine this is how the stage view works), but we also want to be able to show on the main dashboard (which is new). So this may be 2 parts: one is in the stage graph data, the other would be part of the overall job status so that it can show up as favourites (just thinking aloud...) jamesdumay so is the data returned indicating the fields required out of scope of this? or in scope? not clear

James Dumay made changes - 2016-09-26 03:32

Link

New: This issue relates to JENKINS-35795 [ JENKINS-35795 ]

Collapse comment: James Dumay added a comment - 2016-09-26 03:42, Edited by James Dumay - 2016-09-26 03:42

James Dumay added a comment - 2016-09-26 03:42 - edited

michaelneale right on - "waiting for input" is just the same as running, success, failure, unstable and unknown run statuses.

Expand comment: James Dumay added a comment - 2016-09-26 03:42, Edited by James Dumay - 2016-09-26 03:42

James Dumay added a comment - 2016-09-26 03:42 - edited michaelneale right on - "waiting for input" is just the same as running, success, failure, unstable and unknown run statuses.

James Dumay made changes - 2016-09-26 03:43

Description

Original: *In Scope* * We need a new run status when the run is waiting for input * Status should be called "waitingForInput" * Any stages or parallels that are waiting on an input step should also have the "waiting for input" status. *Context* We are showing any runs "waiting for input" with their own status indicator. Don't worry if the UI hasn't mapped it.

New: *In Scope* * We need a new run status when the run is waiting for input * Status should be called "waitingForInput" * A pipeline's run and any stages or parallels can have the status "waiting for input" so long as it contains one or more input steps waiting for input. *Context* We are showing any runs "waiting for input" with their own status indicator. Don't worry if the UI hasn't mapped it.

Collapse comment: James Dumay added a comment - 2016-09-26 03:45

James Dumay added a comment - 2016-09-26 03:45

michaelneale yes, all of that is in scope. I've updated the scoping in the description to eflect that.

Expand comment: James Dumay added a comment - 2016-09-26 03:45

James Dumay added a comment - 2016-09-26 03:45 michaelneale yes, all of that is in scope. I've updated the scoping in the description to eflect that.

Load more newer events