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

Move published artifacts to google storage #4183

Closed
mhagen-vmware opened this issue Mar 8, 2017 · 4 comments · Fixed by #5024
Closed

Move published artifacts to google storage #4183

mhagen-vmware opened this issue Mar 8, 2017 · 4 comments · Fixed by #5024
Assignees
Labels
component/test Tests not covered by a more specific component label priority/p2
Milestone

Comments

@mhagen-vmware
Copy link
Contributor

User statement: As an engineer and customer of VIC, I want the builds artifacts to be published in an accessible and supported location

Details: We have decided to consolidate our image and binary storage locations and google has been chosen. We need to move the publishing over to the new location and orchestrate all the documentation and nightly testing and any other scripts that are pointing to bintray need to be moved in relatively close order. The change should be fairly easy using this guide:
https://github.com/drone-plugins/drone-google-cloudstorage/blob/master/DOCS.md

Acceptance criteria: Build artifacts and documentation all point to google cloud storage.

@mhagen-vmware mhagen-vmware added component/test Tests not covered by a more specific component label priority/p2 labels Mar 8, 2017
@mhagen-vmware
Copy link
Contributor Author

@stuclem ^^ doc requirement

@mhagen-vmware
Copy link
Contributor Author

@stuclem @karthik-narayan I am actively working on this story, and I am almost done. If all goes well, I should have a PR out today or tomorrow, which I will also tag you in.

@stuclem
Copy link
Contributor

stuclem commented May 4, 2017

OK, thanks for the heads-up @mhagen-vmware

@karthik-narayan
Copy link

I'll be on the lookout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/test Tests not covered by a more specific component label priority/p2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants