Open joverlee521 opened 1 month ago
At first I thought this would be pretty straight-forward:
nextstrain build . --report
report.html
to the list of paths for the build artifactHowever, the command nextstrain build . --report
will not always work since the run
input allows any arbitrary shell command, e.g. if the run command is nextstrain build ingest ...
, we would need to run nextstrain build ingest --report
.
For non-aws-batch runtimes, I think this can be achieved directly through the run
input
run: nextstrain build ingest; nextstrain build ingest --report
We cannot follow the same pattern in the aws-batch
runtime because of the wait for the AWS Batch job to finish...
Ah, we can download the Snakemake files into the current dir then generate the report (dependent on release with https://github.com/nextstrain/cli/pull/374):
nextstrain build --aws-batch --attach <job-id> --download ".snakemake/" . ;
nextstrain build . --report
I think this does not have to be built into the pathogen-repo-build
workflow as it can just be run as a separate job in the caller workflow (small block on https://github.com/nextstrain/.github/issues/79)
I guess we can see how helpful Snakemake reports are for now with these alternative methods of generating them before we add more complexity to the pathogen-repo-build
workflow.
(dependent on release with nextstrain/cli#374):
@joverlee521 Want to release 8.5.0 of Nextstrain CLI?
(dependent on release with nextstrain/cli#374):
@joverlee521 Want to release 8.5.0 of Nextstrain CLI?
Yup! Will do ~now.
Context
Originally proposed in https://github.com/nextstrain/cli/issues/373#issuecomment-2174603786
It'd be helpful to have a summary of workflow stats in the form of a Snakemake report for our automated pathogen workflows.