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

Automation: Generate both global and wa-state phylogenetic trees #54

Merged
merged 4 commits into from
Jan 20, 2025

Conversation

j23414
Copy link
Collaborator

@j23414 j23414 commented Jan 10, 2025

Description of proposed changes

During automated building, kick off both global and wa (washington-state) phylogenetic trees.

Main changes include:

  • Configuration updates: Modifies the phylogenetic workflow such that the "global" and "wa" pipeline-generated files are placed in subfolders and do not overwrite each other. Build names are explicitly specified from the config YAML files.
  • Automation: Adds a phylogenetic_wa GitHub Action to support building both global and Washington state phylogenetic trees and deploys them to WNV_global and WNV_wa respectively. See commits for details.

Checklist

  • Checks pass
  • Manual checks pass

@j23414 j23414 force-pushed the multi-builds branch 3 times, most recently from b50253f to 8c9b810 Compare January 10, 2025 22:28
@j23414 j23414 changed the title [draft] Multi builds Automation: Generate both global and wa-state phylogenetic trees Jan 11, 2025
@j23414 j23414 marked this pull request as ready for review January 13, 2025 20:47
…wa) builds

This is a prerequisite to automating both global and washington state builds
so that they do not overwrite to the same files.
Added a `phylogenetic_wa` GitHub Action in order to support building both
global and Washington state phylogenetic trees. Since both define custom_rules,
which would overwrite each other, we defined a config-public.yaml that combines
deploy-related and Washington state-specific custom rules, merging them into
a unified array.

For the Washington state build, the public-facing configuration required
additional overrides to access data from the public site, as opposed to
the original configuration, which relied on privately processed ingest.
@j23414
Copy link
Collaborator Author

j23414 commented Jan 20, 2025

Merging this, since:

@j23414 j23414 merged commit 19f50ac into main Jan 20, 2025
4 checks passed
@j23414 j23414 deleted the multi-builds branch January 20, 2025 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant