You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
@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?
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
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.
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
The text was updated successfully, but these errors were encountered: