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

CI: Switch CI to pathogen-repo-ci workflow #70

Merged
merged 2 commits into from
Jul 16, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
ingest: Add CI build config
The ingest workflow current runs in <1 minute so I figured it'd be nice
to add as an additional check in the GH Action CI workflow.
If the ingest workflow ever runs for too long, we should figure out a
way to subset the ingest data.

The CI build config includes a bogus key because Snakemake requires the
config file to have at least one top level key.

Previous CI run without the bogus key ran into an error¹
```
snakemake.exceptions.WorkflowError: Config file must be given as JSON or YAML with keys at top level.
```

¹ <https://github.com/nextstrain/zika/actions/runs/9948628997/job/27483549394#step:9:17>
  • Loading branch information
joverlee521 committed Jul 16, 2024
commit 44f27a5670e391b4a5df93ba56d08e2d99fa415c
6 changes: 6 additions & 0 deletions ingest/build-configs/ci/config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# TODO: If the ingest workflow ever runs too long, we should figure out a way
# to subset the ingest data. Currently, the CI just runs the default ingest workflow.

# Snakemake requires at least one top level key in a config file, so including
# a bogus key here that should not be used anywhere in the Snakemake workflow
bogus_ci_config: "bogus_ci_config"