[build2] build2 Action for GitHub Workflows
Fabian Meyer
fabian.meyer at posteo.de
Wed Apr 13 20:27:06 UTC 2022
Hi Boris,
thanks for the feedback. Just switched the install process for Unix
systems to the offline version, which gave the whole things some
speed-up. It is now possible to specify either "latest", "staged" or an
explicit version for the action.
Still using the install script though. What's the actual benefit of
using the scripts inside the archives directly?
Windows is still open, I will look into that when I have more time.
Powershell is not my favorite shell after all :D.
Sure, I would love to move the GitHub Action to the build2 organization
and become a contributor.
You would have to tell me how I / you / we can move the repo. Or will
you just fork it?
Anyway, I will be busy during the easter weekend, so I won't be
reachable that well until Monday / Tuesday.
Regards
Fabian
On 4/13/22 13:15, Boris Kolpackov wrote:
> Fabian Meyer via users <users at build2.org> writes:
>
>> I just wanted to let the community know that I created a GitHub
>> Workflows Action for setting up build2 with Ubuntu, and Windows
>> runners.
> Nice, I took a cursory look, and I have a couple of suggestions:
>
> 1. You could get rid of the hardcoded default option by downloading
> and examining https://download.build2.org/toolchain.sha256
>
> This file will always be there and will always be pointing to
> the latest release.
>
> As a bonus, you could easily make your action support the staged
> toolchain (e.g., by specifying "staged" instead of the version).
> Its toolchain.sha256: https://stage.build2.org/0/toolchain.sha256
>
> FYI, this is how our own CI infrastructure discovers the toolchain
> locations.
>
> 2. You can substantially speed things up by performing local installation:
>
> https://build2.org/install-faq.xhtml#offline
>
> In fact, I would probably go a step further and skip the install
> script and go directly to build2-toolchain-X.Y.Z.tar.xz (plus
> build2-baseutils on Windows) and use the build{.sh,*.bat} scripts
> inside directly (which is what the install scripts ultimately do).
>
> Also let me know if you would be interested in transferring this project
> to the github.com/build2/ organization (you will still be the owner). Then
> we would be able to make it "official" GitHub action for build2 and link
> to it from build2.org. Let me know if you are interested and I will send
> you an invite to join the organization.
More information about the users
mailing list