Skip to content
This repository has been archived by the owner on May 8, 2024. It is now read-only.

[New Feature]: Execution of CHIRP CWL workflow #260

Open
LucaCinquini opened this issue Jan 17, 2024 · 4 comments
Open

[New Feature]: Execution of CHIRP CWL workflow #260

LucaCinquini opened this issue Jan 17, 2024 · 4 comments

Comments

@LucaCinquini
Copy link
Collaborator

LucaCinquini commented Jan 17, 2024

Acceptance Criteria:
o Demonstrated execution of CHIRP workflow triggered from the Airflow UI and/or Airflow API
o CI/CD pipeline for nightly execution of CHIRP workflow

Dependencies:
From DS: all data services installed and configured on mcp-venue-dev and mcp-venue-test

@GodwinShen
Copy link

@ngachung, I noticed that @LucaCinquini has your U-DS deployment marked as a dependency but I don't see a corresponding ticket on your end to track that work. I believe we discussed the status on your deployment work at yesterday's status meeting, when do you think you'll be done with that work so that @LucaCinquini and his team can proceed with this ticket?

@ngachung
Copy link

Deployment to MCP Shared Services Test and Venue Test will be completed by EOD 2/26. We're tracking the deployment work in unity-sds/unity-data-services#323

@LucaCinquini
Copy link
Collaborator Author

We should ask @mike-gangl to test the CHIRP workflow with the new Unity Data Services on the DEV venue before attempting to execute it within the SPS+Airflow system. Assuming we still want to support CHIRP.

@GodwinShen
Copy link

@mike-gangl to try this out on DEV per the comment above from @LucaCinquini

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: Todo
Development

No branches or pull requests

3 participants