• Type: Improvement
• Resolution: Fixed
• Priority: Major
• Component/s: pipeline-input-step-plugin
• Labels:

  None

[JENKINS-40926] Persist accepted input values

James Dumay created issue - 2017-01-09 22:03

James Dumay made changes - 2017-01-09 22:03

Issue Type

Original: Bug [ 1 ]

New: Improvement [ 4 ]

James Dumay made changes - 2017-01-09 22:04

Link

New: This issue blocks JENKINS-40672 [ JENKINS-40672 ]

James Dumay made changes - 2017-01-09 22:10

Description

Original: *Use case* Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed. Today the input step throws away the execution data which means we are unable to later display it to the user.

New: *Use case* Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed. Today the input step throws away the execution data which means we are unable to later display it to the user. If the Input Step persisted its execution and values then we could build a good API for this.

James Dumay made changes - 2017-01-09 22:10

Description

Original: *Use case* Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed. Today the input step throws away the execution data which means we are unable to later display it to the user. If the Input Step persisted its execution and values then we could build a good API for this.

New: *Use case* Developers would like to see the provided input parameters in the UI after the execution of the input step has been completed. This provides additional context about who proceeded on input and what parameters were passed. Today the input step throws away the execution data which means we are unable to later display it to the user. If the Input Step persisted its execution and values then we could build a UI for this.

Collapse comment: Andrew Bayer added a comment - 2017-04-05 23:02

Andrew Bayer added a comment - 2017-04-05 23:02

So we do have the user via ApproverAction, but only for the whole Run. So we need to expand that to the other parameters and save it to the FlowNode as well.

Expand comment: Andrew Bayer added a comment - 2017-04-05 23:02

Andrew Bayer added a comment - 2017-04-05 23:02 So we do have the user via ApproverAction , but only for the whole Run . So we need to expand that to the other parameters and save it to the FlowNode as well.

Andrew Bayer made changes - 2017-04-05 23:19

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Andrew Bayer made changes - 2017-04-05 23:19

Assignee

New: Andrew Bayer [ abayer ]

Andrew Bayer made changes - 2017-04-05 23:41

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Collapse comment: Andrew Bayer added a comment - 2017-04-05 23:41

Andrew Bayer added a comment - 2017-04-05 23:41

Initial PR up at https://github.com/jenkinsci/pipeline-input-step-plugin/pull/12

Expand comment: Andrew Bayer added a comment - 2017-04-05 23:41

Andrew Bayer added a comment - 2017-04-05 23:41 Initial PR up at  https://github.com/jenkinsci/pipeline-input-step-plugin/pull/12

Andrew Bayer made changes - 2017-04-05 23:41

Remote Link

New: This issue links to "PR #12 (Web Link)" [ 15906 ]

Load more newer events