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.

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

Fix s3 deploy when branches have same prefix as other branch. #4184

Merged
merged 1 commit into from Aug 9, 2016

Conversation

mramato
Copy link
Contributor

@mramato mramato commented Aug 8, 2016

Turns out our deploy step had a nasty bug where branches would collide if they started with the name of another branch, for example 3d-tiles would try and delete the deployment files for 3d-tiles-transform. This is because AWS prefixes need to end with a trailing / in order to list only child files. So 3d-tiles would return all files from all branches that start with 3d-tiles, whereas 3d-tiles/ only gets files from
3d-tiles as desired.

Ones this is merged down into 3d-tiles and related branches, all of the CI processes should finally start to pass.

Turns out our deploy step had a nasty bug where branches would collide if
they started with the name of another branch, for example `3d-tiles` would
try and delete the deployment files for `3d-tiles-transform`.  This is
because AWS prefixes need to end with a trailing `/` in order to list
only child files.  So `3d-tiles` would return all files from all branches
that start with `3d-tiles`, whereas `3d-tiles/` only gets files from
`3d-tiles` as desired.
@lilleyse lilleyse merged commit b6421ed into master Aug 9, 2016
@lilleyse lilleyse deleted the fix-deploy branch August 9, 2016 14:20
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.

None yet

2 participants