LFIT Jenkins transition to GHA POC

[vvalderrv]

While acknowledging that transitioning all pipelines and jobs to GitHub Actions (GHA) may not be practical, recent GH changes to self-hosted and free runners along with container options create opportunities for a more extensive migration of pipelines and jobs. With this in mind, as part of the Sovereign Tech Fund initiative, we would like to do a POC for the BWG and are requesting admin access to github.com/nodejs

GitHub
username: lfreleng-github

Thank you,
Vanessa Valderrama
LF Release Engineering

[targos]

What kind of actions do you need to do that require admin access to the org?

[vvalderrv]

As we develop our transition plan, we're actively seeking opportunities to streamline our vendor relationships by consolidating services wherever feasible.

One avenue for achieving this consolidation is through maximizing our utilization of GHA. By leveraging GHA to its fullest extent, we aim to reduce reliance on external vendors and simplify our tooling landscape. This approach aligns with the STF initiative to consolidate vendors (in this case, cloud vendors), reduce costs, and standardize wherever possible.

In facilitating the POC, LFIT will not be modifying any existing GH configurations or workflows. However, to effectively implement new workflows, we will require administrative access to view current configurations and to add additional configurations, variables, and secrets as necessary.

Thank you,
Vanessa Valderrama
LF Release Engineering

[mcollina]

I don't think it's worthwhile to do a PoC for this. Given how GHA works and the need for the same infrastructure to run for both nodejs and nodejs-private (nodejs-private is a separate GitHub organization that we create security releases from), I have a rough feeling that migrating out of Jenkins is either a task of gargantuan proportion or just infeasible.

My 2 cents is that money and effort would be better allocated elsewhere.