-
Notifications
You must be signed in to change notification settings - Fork 2
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
Clean up workflows #62
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Trim back CI jobs for reasons stated in nextstrain/cli@fab709a
Remove the copy in this repo and update references. The supporting scripts `sha256sum` and `cloudfront-invalidate` can also be removed.
Remove the copies in this repo and update references.
No longer need to create an envdir with ingest/bin/write-envdir to use with --exec env + `envdir env.d snakemake`. Moves the env variables in the GitHub Action workflow to the step that needs them to limit scope of their availability. Note the `PAT_GITHUB_DISPATCH` envvar was removed because we no longer trigger any downstream actions since b5fc2b9
The model results are expected to be uploaded to the same AWS S3 bucket, so remove the unnecessary complexity caused by the nested `s3_dst` config param. This will make it easier to transition to using the pathogen-repo-build workflow for the run-model GitHub Action.
Since the workflow config has been updated in the previous commit to use a top level `s3_dst` param, we can now easily override it in the GH Action workflow with input values for trial runs. This allows us to directly use the reusable pathogen-repo-build workflow. Note that `DATA_PROVENANCES` and `S3_DST` are passed as envvars to the reusable workflow so they can be interpolated in the build command, but they do _not_ need to be passed to the build runtime. Removed `bin/set-trial-optional-config` since we are no longer using a full config file to override the workflow configs.
joverlee521
force-pushed
the
clean-up
branch
from
September 7, 2023 22:59
d5971c8
to
c01db93
Compare
This was referenced Sep 7, 2023
Merging since test runs worked fine, will monitor automated runs tomorrow. |
Following up here that all automated workflows ran as expected last night and this morning. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
General clean up of workflows that includes:
s3_dst
config paramSee commits for details
Checklist