Skip to content
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

ansible: don't assume the relative paths for staging & dist are the same #3947

Merged
merged 1 commit into from
Nov 4, 2024
Merged

ansible: don't assume the relative paths for staging & dist are the same #3947

merged 1 commit into from
Nov 4, 2024

Commits on Nov 4, 2024

  1. ansible: don't assume the relative paths for staging & dist are the same 

    Some non-mainline releases' src dirs differ from their dst dirs (i.e.
v8-canary builds upload to `/home/staging/nodejs/custom` and then are
promoted to `/home/dist/nodejs/v8-canary`. This wasn't being accounted
for when we promoted files from the `dist-staging` bucket to the
    `dist-prod` bucket.

Signed-off-by: flakey5 <[email protected]>
    @flakey5
    flakey5 committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    f2078cb View commit details
    Browse the repository at this point in the history