search

rakudo / star

Rakudo Star (Raku distribution)
https://rakudo.org/
Artistic License 2.0
267 stars 41 forks source link

Revert "Revert "Signing"" #177

Closed patrickbkr closed 2 years ago

patrickbkr commented 2 years ago

This reverts commit 8c8d72dca3f98d41c4ed942e35024dd5bce34c52.

I have set the two related secrets again (GPG_PRIVATE_KEY and PASSPHRASE) in this repository as well as patrickbkr/star. A build in patrickbkr/star works as it did before. My best guess is thus, that the secrets in rakudo/star were somehow flawed.

@AntonOks Do you know whether there is a way to try out the build without doing another release?

AntonOks commented 2 years ago

Do you know whether there is a way to try out the build without doing another release?

No, but we can build the same release again and again... as long as it's the "latest" everywhere (rakudo/rakudo, NQP, Moar,...) and no one changes the "modules.txt" in-between (which unfortunately anyhow no one "maintains")...

patrickbkr commented 2 years ago

@AntonOks OK. Then I'd say we do just that.

patrickbkr commented 2 years ago

@AntonOks You already triggered a new run, thanks. Can you explain what I missed?

AntonOks commented 2 years ago

@AntonOks You already triggered a new run, thanks. Can you explain what I missed?

a (Rakudo version-like) TAG , see https://github.com/rakudo/star/blob/a541401096756ff151f365eb7d45610037c1b194/.github/workflows/build_rakudo-star.yml#L91

There are several ways how-to fire a auto build... I think I need to take some time and write things down :O ... let's do it quick-n-dirty here for now / you ;)

  1. The "git" common way you clone the repo, add a new (release) tag and push it, see https://github.com/AntonOks/rakudo-star-win#as-a-github-action-workflow this will fire the build_rakudo-star.yml workflow, where the pushed TAG will be used, see above
  2. You edit and change https://github.com/rakudo/star/blob/a541401096756ff151f365eb7d45610037c1b194/.github/workflows/build_rakudo-star.yml#L91 and fire the buildrakudo-star.yml workflow **!!! Make sure you revert this change afterwards again !!!_**
  3. You ensure the "latest" rakudo/rakudo release, say 2022.06, doesn't exist as a TAG in the STAR repo... and then just fire the sync_latest_rakudo_release.yml workflow this one will "only" create the new "release TAG", say 2022.06, in the STAR repo... which again triggers the formerly mentioned build_rakudo-star.yml workflow
  4. Finally there is https://github.com/AntonOks/cronactions/blob/main/.github/workflows/publish_rakudo-star_on_rakudo.org.yml which will compare the latest Rakudo.org STAR version with the GH rakudo/star release... and copy if over if needed :) will move this workflow also into the GH rakudo/star repo later
patrickbkr commented 2 years ago

Thanks for the explanation!