search

Raku / nqp

NQP
Other
336 stars 131 forks source link

question / offer: build GitHub workflow based NQP releases #818

Open AntonOks opened 5 months ago

AntonOks commented 5 months ago

Hi.

Same question / offer as for MoarVM builds... would someone want to have GitHub workflow based NQP releases to (double) verify things are going well for NQP?!

If this makes sense for you / someone, I'd happily add the same GH workflow here... Let me know.

Thanks & regards

lizmat commented 5 months ago

Yes, please!

jdv commented 5 months ago

What exactly are the motivations here?

From my perspective, (release manager) this only complicates the release process. Does anyone use these extra builds?

Same goes for the moarvm case (I didn't get a chance to look at it before it was merged).

AntonOks commented 5 months ago 
        Hi Justine.This builds have nothing to do with the official Rakudo release process.no change or whatever else is desired / expected / needed.See it as an extra test to proof that some crucial software is successfully build on all the available official GitHub OS‘es. And build logs are also available right where the source is… in case something goes wired with the (GH) builds, a broader community is empowered to check what’s wrong and maybe help.I know Rakodo releases are not officially build on GitHub but Azure… and I‘m‘ aware the runner / node OS versions are usually the same on GitHub and on Azure… but nevertheless there were issues with new GitHub runner OS releases past and their workflow / actions backend in the… that’s the reason why I build the Star Windows MSI package still on Windows 2019.Talking about this…The Star releases ARE build on GitHub and then copied to the proper download area on rakudo.org Would a Star build fail in the future, I would quickly check if the build of the real source of NQP MoarVM also  failed (for the same „git tag“) and if the issue is maybe already known..So, again and in short… just an easily done extra check, specifically related to GitHub CI/CD pipeline builds…Am 29.03.24 um 15:22 schrieb Justin DeVuyst

                Von: "Justin DeVuyst" ***@***.***>Datum: 29. März 2024An: "Raku/nqp" ***@***.***>Cc: "Author" ***@***.***>,"Anton Oks" ***@***.***>Betreff: Re: [Raku/nqp] question / offer: build GitHub workflow based NQP releases (Issue #818)

What exactly are the motivations here? From my perspective, (release manager) this only complicates the release process. Does anyone use these extra builds? Same goes for the moarvm case (I didn't get a chance to look at it before it was merged).

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>