I am for whatever suits better the contributors. GHA seem to be more probable to be "owned" by the developers and is something that can be grasped more easily.
What would be really cool and helpful would be if both GHA and Jenkins CI could use a single build image? (Our own, maintained and tweaked to our needs). We already use such in Jenkins - quay.io/kiegroup/kogito-ci-build , would be similar approach possible in GHA? It would remove my concerns of things going out of sync if both CI environments are executed together. Regards Jan Dne pá 10. 11. 2023 19:59 uživatel Alex Porcelli <[email protected]> napsal: > I'm ok with that, and it seems very much aligned with Apache direction. > > One concern is, how to maintain different tech stacks for CI in sync > and what's the burden that it brings to us... > > At the same time, I understand and agree on the power of GHA. > > > On Fri, Nov 10, 2023 at 1:47 PM ricardo zanini fernandes > <[email protected]> wrote: > > > > Hey folks! > > > > As you know, we are currently working on the CI migration from KIE org to > > Apache. While doing this, I could find some duplication in the Jenkins > > pipelines and GHA in a few repositories. > > > > I propose to focus our flow and automation on GHA while working on > > non-release pipelines. For example tests, checks, validation, PR > > automation, and so on. It's way easier to configure everything on GHA > > directly. Just bear in mind that only verified actions are valid in this > > context. > > > > For Jenkins, we can let the nightly builds verify if we have a healthy > > ecosystem and the release work itself. > > > > wdyt? > > > > -- > > Ricardo Zanini Fernandes > > Vida longa e próspera. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
