-
Notifications
You must be signed in to change notification settings - Fork 33
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
Final github.com publishing things #42
Comments
https://docs.travis-ci.com/user/build-stages/ could be rescue. |
Steps:
|
Noticed that this is an outstanding issue. I was wondering if we wanted to include md5 checksums in the CI pipeline for 0.6.0 @hrw? Does not look to be that complicated, but we could generate the checksums in either |
I think that generation of checksums for release should be part of CI workflow. |
Sounds good. That's what I was thinking too. I'll see about adding it as part of the workflow as a step. |
just came across this issue as it seems that http://download.cirros-cloud.net/version/released is not being updated for the latest |
done. thanks for pointing that out. |
#5 got publishing of releases over to github.
But there are a few other things that I was still (manually) doing when I did a release:
a.) updating https://download.cirros-cloud.net/version/devel and version/released files.
These are just "latest" files and simple text. Easy to update.
b.) updating stream data
bin/mirror-dump-sstream-data
usage shows how I would do this:Unfortunately, mirror-dump-sstream-data basically required access to
all the content so it can generate sums.
sstream data is basically an index of content available. Ubuntu uses it to distribute images. For cirros, the most obvious benefit is the ability to add it as an lxc remote. See 888e7f3 for example.
The text was updated successfully, but these errors were encountered: