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
Now that the GH Action job stays attached and reflects the AWS Batch job status, it should be possible to automate the trigger of the deploy workflow after the builds completed.
I briefly looked into this today and realized this would require the pathogen-repo-build workflow to output the AWS Batch job ID to pass as an input to the deploy workflow.
The text was updated successfully, but these errors were encountered:
Currently, when a private nextflu build completes, we have to manually trigger the deploy private nextflu workflow with the AWS Batch job ID.
Now that the GH Action job stays attached and reflects the AWS Batch job status, it should be possible to automate the trigger of the deploy workflow after the builds completed.
I briefly looked into this today and realized this would require the pathogen-repo-build workflow to output the AWS Batch job ID to pass as an input to the deploy workflow.
The text was updated successfully, but these errors were encountered: