Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a icav2 launch wrapper script for cttsov2 and bclconvert qc pipeline services #289

Closed
alexiswl opened this issue May 8, 2024 · 1 comment · Fixed by #337
Closed
Assignees
Labels
pipeline Workflow/Pipeline Manager

Comments

@alexiswl
Copy link
Member

alexiswl commented May 8, 2024

Issue

As we put more workflows on the system, we can see patterns evolving... which we can turn into constructs to improve the consistency across different services:

Given the following step function:

Details

image

The following top half is generic for all ICAv2 workflow launches:

Details

image

Followed by a very specific ctTSOv2 Launch process:

Details

image

Followed by a generic push event step:

Details

image

Solution

Instead, the generic step function should be a construct that then calls the specific cttso state machine step.

@victorskl victorskl added the pipeline Workflow/Pipeline Manager label May 11, 2024
@alexiswl alexiswl linked a pull request May 15, 2024 that will close this issue
8 tasks
@alexiswl
Copy link
Member Author

This has been generated in the refactoring process of #192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pipeline Workflow/Pipeline Manager
Projects
None yet
2 participants