Skip to content

ci: upload binaries as workflow artifacts #4484

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

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

erikgb
Copy link
Contributor

@erikgb erikgb commented Jan 10, 2025

Closes

What changed?

Slightly improve the upload binary CI job. Since I couldn't find a way to create a "generic" GH package, I suggest starting by replacing the out-commented AWS S3 upload with upload-artifact-action. This will keep the binaries available for the default project retention period (30 days)?

Why was this change made?

I have accidentally reformatted this code several times in other PR, and in general I am not a big fan of out-commented code. We can always find old things in the Git history.

How was this change implemented?

How did you validate the change?

Release notes

Documentation Changes

@erikgb erikgb force-pushed the upload-binary branch 3 times, most recently from c0c5eb2 to 43052f9 Compare January 12, 2025 14:11
@erikgb erikgb enabled auto-merge (rebase) January 13, 2025 08:53
@erikgb erikgb merged commit e98cc76 into weaveworks:main Jan 13, 2025
13 checks passed
This was referenced Jan 15, 2025
This was referenced Feb 4, 2025
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