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

Final github.com publishing things #42

Open
smoser opened this issue Feb 3, 2020 · 7 comments
Open

Final github.com publishing things #42

smoser opened this issue Feb 3, 2020 · 7 comments
Labels
to automate Thing we should put on CI one day

Comments

@smoser
Copy link
Member

smoser commented Feb 3, 2020

#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:

    # this is now moved to git
    $ git clone https://git.launchpad.net/simplestreams
    $ git clone https://github.com/cirros-dev/cirros.git

    $ ./cirros/bin/mirror-dump-sstream-data "\$mirror_d" > mdata.txt
    $ ./simplestreams/tools/tenv tab2streams mdata.txt cirros-streams.d

    $ ./simplestreams/tools/tenv env -u GNUPGHOME \
       $ SS_GPG_BATCH=1 SS_GPG_DEFAULT_KEY=A5DDB840  \
       $ js2signed cirros-streams.d

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.

@hrw
Copy link
Collaborator

hrw commented Feb 6, 2020

https://docs.travis-ci.com/user/build-stages/ could be rescue.

@hrw
Copy link
Collaborator

hrw commented Feb 6, 2020

Steps:

  • build + deploy artifacts
  • fetch artifacts + md5sum + whatever-with-files + deploy MD5SUMS and whatever-needed

@hrw hrw changed the title Final gitub.com publishing things Final github.com publishing things Mar 3, 2020
@hrw hrw added the to automate Thing we should put on CI one day label Mar 3, 2020
@NucciTheBoss
Copy link
Contributor

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 bin/build-release, or in the GitHub Actions workflow and then upload them with the other artifacts. Let me know your thoughts.

@hrw
Copy link
Collaborator

hrw commented Aug 29, 2022

I think that generation of checksums for release should be part of CI workflow.

@NucciTheBoss
Copy link
Contributor

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.

@do3meli
Copy link

do3meli commented Aug 18, 2023

just came across this issue as it seems that http://download.cirros-cloud.net/version/released is not being updated for the latest 0.6.2 release. @smoser might i kindly ask you to look into this again or at least manually update the released file?

@smoser
Copy link
Member Author

smoser commented Aug 18, 2023

just came across this issue as it seems that http://download.cirros-cloud.net/version/released is not being updated for the latest 0.6.2 release. @smoser might i kindly ask you to look into this again or at least manually update the released file?

done. thanks for pointing that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to automate Thing we should put on CI one day
Projects
None yet
Development

No branches or pull requests

4 participants