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

Automate deployment of private nextflu.org site #159

Open
joverlee521 opened this issue Apr 5, 2024 · 0 comments
Open

Automate deployment of private nextflu.org site #159

joverlee521 opened this issue Apr 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@joverlee521
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant