console

console copied to clipboard

When interacting with Pipelines/PipelineRuns in the developer perspective, it is not currently possible to move a PipelineRun with the status "PipelineRunPending" to the running state.

It would be appropriate for users to have the ability to run Pipelines that are currently in the pending state w/o creating an entirely new PipelineRun. Some screenshots are included below where I would expect to see a "Run" option.

cc @eriknelson @mturley

cc @christianvogt @serenamarie125

cc @karthikjeeyar

Yeah, we have a RFE for Resuming the pipelinerun here https://issues.redhat.com/browse/RFE-2423, will add this feature soon.

@karthikjeeyar Is it possible to split that RFE into it's component pieces? We don't need UI support for creating PipelineRuns that are in the PipelineRunPending state. We need UI support for resuming PipelineRuns.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

I think this is worth revisiting since splitting the RFE such that this piece could be merged first would improve the user experience in Migration Toolkit for Red Hat OpenShift in the short term.

/remove-lifecycle stale

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

As best I understand, this is still a valid issue.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.