I am writing to report our recent progress and hopefully respond to Ricardo's question.
Firstly this thread deals with ASF Jenkins jobs, based on github.com/apache/incubator-kie-kogito-pipelines framework. The repository that Ricardo mentions has been adjusted yesterday on the main branch (check latest commits). The overall status of ASF Jenkins jobs at the moment is: 1. Initial job generation from main branches has succeeded after some problems were resolved during today. 2. PR checks, to the best of my knowledge, are correctly being triggered (if some repository was missed, please reach out). 3. There were libraries missing in our kogito-ci-build image as well as network issues when running testcontainers - these 2 are now addressed with at least temporary fixes and jobs should behave correctly. Please let me know in case a PR check fails for your PR in the following days. ------ now plan for following days 4. Enable nightly builds in default env possibly together with Apache nexus snapshot deployment. Regarding GitHub Actions - they are not part of this task as noted above. At the same time they are defined, handled and should be also maintained within particular repository contributors. There are significant limitations coming from the Apache organization GitHub Actions environment, both performance (limited capacity) and origin (there is a restriction on where the implementation of used actions should reside, basically the default ones, apache and a few exceptions). We can start a new thread if needed for GHA. But you can also search [email protected] maling list for related discussions ( https://lists.apache.org/thread/3vw3rdxw8yxj9rlpodksv4wmc3cqmoyo , https://lists.apache.org/thread/84wbzldr4gpvbgwdppw7mclbw7ovtkpp ) and docs ( https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status#GitHubActionsstatus-Security ) Contributions are welcome. Regards Jan On Wed, 20 Sept 2023 at 17:12, ricardo zanini fernandes < [email protected]> wrote: > 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 > > > > > >
