Bug #3990
closed
[Workbench] "Re-run pipeline" buttons should put the new pipeline-instance in the same project as the original
Description
It's very difficult to organize the pipeline instance reruns because there is no GUI way to specify which project to rerun a pipeline instance in, there is no (obvious) GUI way to move a pipeline instance once it has started running, and the default is the home project.
Related issues
Updated by Tom Clegg over 9 years ago
- Subject changed from Re-run with latest and Re-run options do not rerun the pipeline-instance in the same project to [Workbench] "Re-run pipeline" buttons should put the new pipeline-instance in the same project as the original
- Story points set to 0.5
Updated by Tom Clegg over 9 years ago
- Target version set to Arvados Future Sprints
Updated by Radhika Chippada over 9 years ago
- Status changed from New to In Progress
- Assigned To set to Radhika Chippada
- Target version changed from Arvados Future Sprints to 2014-10-08 sprint
When the current project is writable by the current user, put the new pipeline instance in the current project.
Updated by Brett Smith over 9 years ago
Just one style/speed comment: instead of saying visit page_with_token(user); visit instance_path, you can just say visit page_with_token(user, instance_path). This will save Capybara a whole round-trip to the server, which seems worthwhile given how much our integration tests are growing.
That's my only nit. This is good to merge, thanks.
Updated by Radhika Chippada over 9 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|commit:4146cc481cec9847eb41d3e5ba7602b4f33d2096.