-
Story
-
Resolution: Fixed
-
Critical
-
-
pacific, atlantic, indian, arctic, tasman, frank
In Scope
- Add new "waitingForInput" status to API for runs, dag and steps
- 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.
- blocks
-
JENKINS-38494 User can see the input form on an input step (UI)
-
- Resolved
-
- relates to
-
JENKINS-35795 API(s) for acknowledging request for user input in a pipeline
-
- Resolved
-
[JENKINS-38491] Add new "waitingForInput" status to API for runs, dag and steps
Epic Link | New: JENKINS-38490 [ 174672 ] |
Rank | New: Ranked higher |
Sprint | New: 26-september [ 101 ] |
Rank | New: Ranked higher |
Link |
New:
This issue relates to |
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. |
Labels | New: api |
Link |
New:
This issue blocks |
Sprint | Original: pacific [ 101 ] | New: pacific, atlantic [ 101, 106 ] |
Rank | New: Ranked higher |