Skip to content

DEVPROD-16721: dual write release files to new bucket #3805

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 14, 2025
Merged

DEVPROD-16721: dual write release files to new bucket #3805

merged 1 commit into from
Apr 14, 2025

Conversation

drichmdb
Copy link
Contributor

@drichmdb drichmdb commented Apr 2, 2025 •
edited
Loading

This commit adjusts our package_goreleaser task to dual write release
artifacts to the new cdn-origin-mongocli bucket. Eventually we will
remove writes to the old downloads bucket from this task.

@drichmdb drichmdb marked this pull request as ready for review April 10, 2025 15:17
@drichmdb drichmdb requested a review from a team as a code owner April 10, 2025 15:17
@drichmdb
DEVPROD-16721: dual write release files to new bucket
bf4394b 
This commit adjusts our package_goreleaser task to dual write release
artifacts to the new cdn-origin-mongocli bucket. Eventually we will
remove writes to the old downloads bucket from this task.
@drichmdb drichmdb force-pushed the dual-write-buckets branch from e0f2c24 to bf4394b Compare April 10, 2025 15:22
@drichmdb drichmdb changed the title testing DEVPROD-16721: dual write release files to new bucket Apr 10, 2025
fmenezes
fmenezes approved these changes Apr 11, 2025
View reviewed changes
Copy link
Collaborator

@fmenezes fmenezes left a comment

Choose a reason for hiding this comment

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

LGTM, unfortunately we may not test this unless we release, there is a way to release unstable versions to this s3 but then someone would need to manually go and delete the files later on.

@drichmdb
Copy link
Contributor Author

I'm totally fine waiting for a real release to test if that's easier!

@blva blva merged commit 6faee00 into mongodb:master Apr 14, 2025
57 of 60 checks passed
@jeroenvervaeke
Copy link
Collaborator

Hi @drichmdb,
This PR seems to have broken our release. Could you please take a look? https://spruce.mongodb.com/task/mongodb_atlas_cli_master_release_atlascli_github_package_goreleaser__atlascli_v1.42.1_25_04_24_10_12_04/logs?execution=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fmenezes fmenezes fmenezes approved these changes

@blva blva blva approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@drichmdb @jeroenvervaeke @fmenezes @blva