Hi folks! Sorry to push, but do we have a ballpark for the kogito-serverless-operator CI migration? It's reasonably simple since there's only one Jenkins job that can be postponed, everything else is simple GHA. I ask because we have many PRs that need to be merged. I can help if needed, just let me know or give me the directions and I'll happily help.
Cheers! -- Ricardo Zanini Fernandes Vida longa e próspera. On Tue, Sep 19, 2023 at 6:26 AM Tibor Zimányi <[email protected]> wrote: > Hi, > > as part of the effort Jan mentioned, I started working on moving the Drools > repository to the Apache parent pom. I will post updates to this thread > about the ongoing work. > > Best regards, > Tibor > > Dňa ut 19. 9. 2023, 11:11 Jan Šťastný <[email protected]> napísal(a): > > > Hello, > > > > we're about to start migrating main branches of repositories containing > > pipeline frameworks and configuration to reflect the recent transfer. > > > > Pipelines will first be configured in reduced scope, starting in order: > > > > 1. Pull-request jobs, reporting outcomes to PRs (only for the main > > branch). > > 2. Nightly builds without nexus deploy of SNAPSHOTs. > > - This is due to the pending move from using jboss-parent to an > > apache parent pom for our projects - that's a pending task that > > needs to be > > done in all our repositories, otherwise release to Apache Nexus > > would be > > blocked. > > - Relevant repositories to be moved to Apache parent pom: > > - incubator-kie-drools (thanks @tzimanyi for taking a look > > already) > > - incubator-kie-kogito-runtimes > > - incubator-kie-kogito-apps > > - incubator-kie-kogito-examples > > - incubator-kie-optaplanner > > - incubator-kie-optaplanner-quickstarts > > - Contributions in these tasks are very much appreciated. > > 3. Nightly builds including nexus deploy of SNAPSHOTs. > > 4. Nightly builds of cloud artifacts including deploy to the registry. > > 5. Nightly builds in non-default environments. > > 6. Release pipelines > > > > Given the disruption of CI caused by the transfer, we're not gonna follow > > the regular PR review process, especially when concerning changes in > > apache_migration branches in respective repositories. > > Once apache_migration branches are ready to be moved to main a regular PR > > will be raised and put on review. > > > > Any progress in the CI setup will be reported in this thread. > > > > Thanks for understanding and patience. > > > > Regards > > Jan > > >
