Skip to content

Commit

Permalink
pathogen-repo-build: use tee -a build.log`
Browse files Browse the repository at this point in the history
I was confused that the CI workflow¹ did not have an AWS Batch Job
summary even though the tests have included an aws-batch runtime since
dab7abc.

The build.log from the build-output-aws-batch artifact² was incomplete
and did not include the AWS Batch Job ID. The build.log only includes
the last part of the build logs, so I suspect it's somehow overwriting
itself.

¹ https://github.com/nextstrain/.github/actions/runs/8209158885?pr=76
² https://github.com/nextstrain/.github/actions/runs/8209158885/artifacts/1310654964
  • Loading branch information
joverlee521 committed Mar 12, 2024
1 parent 0f43b8f commit c36f89b
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/pathogen-repo-build.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -276,7 +276,7 @@ jobs:
# shellcheck disable=SC2154
set -x
eval "unbuffer $NEXTSTRAIN_BUILD_COMMAND" |& tee build.log
eval "unbuffer $NEXTSTRAIN_BUILD_COMMAND" |& tee -a build.log
# Attempt to get the AWS Batch ID even if the run build command failed
# as long as the runtime is `aws-batch` and the `build.log` file exists
- if: ${{ always() && inputs.runtime == 'aws-batch' && hashFiles('build.log') != '' }}
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/pathogen-repo-build.yaml.in
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ jobs:
# shellcheck disable=SC2154
set -x

eval "unbuffer $NEXTSTRAIN_BUILD_COMMAND" |& tee build.log
eval "unbuffer $NEXTSTRAIN_BUILD_COMMAND" |& tee -a build.log

# Attempt to get the AWS Batch ID even if the run build command failed
# as long as the runtime is `aws-batch` and the `build.log` file exists
Expand Down

0 comments on commit c36f89b

Please sign in to comment.