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(gcb): Correctly fetch artifact manifest when it contains a version #468

Merged
merged 1 commit into from
Jun 20, 2019
Merged

fix(gcb): Correctly fetch artifact manifest when it contains a version #468

merged 1 commit into from
Jun 20, 2019

Conversation

ezimanyi
Copy link
Contributor

The logic to fetch an artifact manifest does not properly account for the GCS path containing a version (as in gs://bucket/file.json#123).

This isn't causing any active issues as GCB creates a file named with a UUID and does not include the version in the build output, but we should properly handle this in case this changes (or in case we re-use the artifact fetching code elsewhere).

The logic to fetch an artifact manifest does not properly account for
the GCS path containing a version (as in gs://bucket/file.json#123).

This isn't causing any active issues as GCB creates a file named
with a UUID and does not include the version in the build output,
but we should properly handle this in case this changes (or in
case we re-use the artifact fetching code elsewhere).
Copy link

@maggieneterval maggieneterval left a comment

Choose a reason for hiding this comment

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

🎣 📜 🐟 ✔️

@maggieneterval maggieneterval merged commit db05a9b into spinnaker:master Jun 20, 2019
@ezimanyi ezimanyi deleted the fix-artifact-version branch June 20, 2019 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants