Actions
Idea #10524
closed
[Crunch2] In Crunch2-only environments, workbench should use "processes" instead of "pipelines and processes" and "workflows" instead of "pipeline templates" as is used in a mixed environment.
Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
-
Target version:
Start date:
11/21/2016
Due date:
Story points:
-
Release:
Release relationship:
Auto
Updated by Radhika Chippada about 8 years ago
- Subject changed from [Crunch2] In Crunch2-only environments, workbench should use "processes" instead of "pipelines and processes" and "workflows" instead of "pipeline templates" as is used in a mixed environment. Refers to #10310 to [Crunch2] In Crunch2-only environments, workbench should use "processes" instead of "pipelines and processes" and "workflows" instead of "pipeline templates" as is used in a mixed environment.
- Description updated (diff)
Updated by Tom Morris almost 8 years ago
- Assigned To set to Radhika Chippada
- Target version set to 2016-11-23 sprint
Updated by Radhika Chippada almost 8 years ago
- Status changed from New to In Progress
Updated by Radhika Chippada almost 8 years ago
Branch 10524-crunch2-workbench is ready at 185bc33b
Test runs @ https://ci.curoverse.com/job/developer-run-tests/75/
Updated by Lucas Di Pentima almost 8 years ago
- I think it would be clearer if the labels are assigned inside a single conditional, avoiding the "double assignment". The
no_jobs_apivar isn't used anywhere else in the templates, so it can be avoided. - Do you think writing some tests to check those alternating labels would be useful? Maybe mocking
PipelineInstance.api_exist?would allow an easy way of testing the changes.
Jenkins tests seem to have had some kind of problem. I ran apps/workbench tests locally without failures.
Updated by Radhika Chippada almost 8 years ago
I think it would be clearer if the labels are assigned inside a single conditional, avoiding the "double assignment".
Updated
Do you think writing some tests to check those alternating labels would be useful? Maybe mocking PipelineInstance.api_exist? would allow an easy way of testing the changes.
Updated controller disabled api test
Thanks.
Updated by Radhika Chippada almost 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:6f461f4d0a996da85140982846a5d5c10ccfaae4.
Updated by Tom Clegg over 5 years ago
- Related to Bug #15014: [Workbench] Hide busy/idle nodes display when crunch1 is not active added
Updated by Tom Clegg over 5 years ago
- Related to deleted (Bug #15014: [Workbench] Hide busy/idle nodes display when crunch1 is not active)
Actions