Hi all, sorry for coming in late to this discussion. In general, Apache would like projects to use the CI/CD infrastructure provided by Apache. This has the simple reason, that in the past it occurred that, when using external infra, the service simply stopped existing, being free or the person/company paying for it stopped paying. Then the project is sort of in a state, where it’s not able to push out new versions.
So currently in order to deploy SNAPSHOT versions, Apache Jenkins would be the place to go, as that’s setup to deploy to repository.apache.org and other repos. I think there’s also an option to do this on GitHub Actions runners, but I’m not that familiar with it. Please reach out to Infra if you’ve got questions regarding that. Chris Von: Alex Porcelli <[email protected]> Datum: Dienstag, 31. Oktober 2023 um 19:00 An: [email protected] <[email protected]> Betreff: Re: [PROPOSAL] Images Publishing and CI Seems reasonable. We need understand and move towards align with Apache direction, which means not publish under kiegroup but in Apache instead. But, as proposed, it’s fine to continue doing it for the short term. On Fri, Oct 27, 2023 at 2:56 PM ricardo zanini fernandes < [email protected]> wrote: > Good question! I think we can, I'm not seeing any problems with this. > > -- > > > > On Fri, Oct 27, 2023 at 3:40 PM Spolti <[email protected]> wrote: > > > We can keep using quay for CI test builds and dockerhub for releases? > > > > Em sex., 27 de out. de 2023 às 14:29, ricardo zanini fernandes < > > [email protected]> escreveu: > > > > > Hello! > > > > > > I'm opening this thread to summarize our discussions around image > > > publishing and CI. The overall planning is: > > > > > > 1. In the short term we can keep using quay.io/kiegroup > > > 2. Verify the images CI PR checks, and the pipelines to publish nightly > > > builds and releases > > > 3. Keep using Cekit [1] > > > 4. Migrate to Dockerhub [2] and rename `sed -i > > > /kogito-serverless-workflow/sonataflow/`. Need to investigate if > > > Dockerfiles are required since Cekit architecture uses a different > > > approach. > > > > > > Do we all agree? > > > > > > I'll start looking at the CI next week, Jakub Schwan is likely to help. > > > > > > Cheers! > > > > > > [1] https://cekit.io/ > > > [2] https://hub.docker.com/u/apache > > > -- > > > > > > > > > -- > > Regards, > > --Filippe > > >
