Skip to content

pathogen-repo-build: Support artifact-paths with AWS Batch#164

Open
victorlin wants to merge 3 commits intomasterfrom
victorlin/artifact-paths
Open

pathogen-repo-build: Support artifact-paths with AWS Batch#164
victorlin wants to merge 3 commits intomasterfrom
victorlin/artifact-paths

Conversation

@victorlin
Copy link
Member

@victorlin victorlin commented Mar 18, 2026

This is now possible with the wait-N jobs.

Should improve debugging experience for workflows using the AWS Batch runtime.

Checklist

@victorlin victorlin self-assigned this Mar 18, 2026
Without this, the workflow execution happens in the run-build job
instead of the wait-N jobs.
@victorlin victorlin force-pushed the victorlin/artifact-paths branch from 6941e1a to bfa71f3 Compare March 18, 2026 20:26
This is now possible with the wait-N jobs.
@victorlin victorlin force-pushed the victorlin/artifact-paths branch from bfa71f3 to e716626 Compare March 18, 2026 20:42
@victorlin victorlin changed the title Support artifact-paths with AWS Batch pathogen-repo-build: Support artifact-paths with AWS Batch Mar 18, 2026
This allows the full build log to be uploaded upon completion, matching
behavior in run-build with local runtimes.
Comment on lines +411 to +418
- if: ${{ always() && steps.attach.outputs.conclusion != 'timeout' }}
uses: actions/upload-artifact@v7
with:
if-no-files-found: warn
name: ${{ inputs.artifact-name }}
path: |
${{ env.NEXTSTRAIN_DEFAULT_ARTIFACT_PATHS }}
${{ inputs.artifact-paths }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm slightly worried about artifact storage limits, which I think is 2GB/repo/month?

The builds we run on AWS Batch are usually the larger builds so these might take up too much storage. I'd rather save the artifact storage space for GitHub Action workflows that are not on AWS since those outputs are not accessible outside for GitHub.

Maybe using artifacts should be an opt-in feature for AWS Batch instead of the default?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, I'll update this PR to make it opt-in.

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.

2 participants