Skip to content

Add upload-artifact-s3 action #6659

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

Open
wants to merge 50 commits into
base: main
Choose a base branch
from
Open

Conversation

zklaus
Copy link

@zklaus zklaus commented May 23, 2025

This adds an updated version of the upload-artifact-s3 action to this repo.

It is based on the original actions/upload-artifact action as well as the currently used seemethere/upload-artifact-s3 action.

However, since the latter is based on a rather old version of the former and because there have been substantial changes to the underlying aws-sdk since then, a lot of the s3 code was rewritten and integrated with the latest version of the original actions/upload-artifact action.

Testing was performed in a separate repository; the logs for the test jobs are available.

This version also adds a few s3 specific features, such as new metadata outputs and s3 acl handling, which are detailed in the README.

This PR replaces half of pytorch/pytorch#6269, the other half being the corresponding download action.

It also addresses part of pytorch/ci-infra#242.

Copy link

vercel bot commented May 23, 2025

@zklaus is attempting to deploy a commit to the Meta Open Source Team on Vercel.

A member of the Team first needs to authorize it.

@facebook-github-bot
Copy link
Contributor

Hi @zklaus!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@atalman
Copy link
Contributor

atalman commented May 27, 2025

Hi @zklaus can we include small README.md file in the .github/actions/upload-artifact-s3/ with the guide on how to update this action to next version ?
Also we should probably drop not used path like everything in .github/actions/upload-artifact-s3/.github/

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 6, 2025
Copy link
Contributor

@atalman atalman left a comment

Choose a reason for hiding this comment

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

lgtm

@zklaus
Copy link
Author

zklaus commented Jun 10, 2025

When this PR gets merged, we should migrate the use of the older action to the newer one. I have created a tracking issue for that at #6755

Copy link
Collaborator

@zxiiro zxiiro left a comment

Choose a reason for hiding this comment

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

Thanks for moving this item along. I know @jwagantall will be happy to see this move forward.

Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

It feels like we are checking a lot of build artifacts into repo, or is it really 208 files large

Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

Sorry, I see that original action was also pretty large

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants