Today I've switched PR checks from Full downstream build to compile downstream build. This should improve execution times slightly. * Project against which the PR is will be run fully with tests. * Projects upstream will be run with the install goal (for artifacts to be available down the stream) and no tests (`quickly` profile) * Projects downstream, will be only compiled, so that a breaking mistake is caught. It should be used carefully when downstream projects are used as validation of the change - this is not a reliable check at this moment.
It's an interim workaround until we have a better handling of PR checks, allowing selectively run different scope of checks on demand. That work has not yet been started, I plan to start drafting that in the following days. When you have a pending PR with checks that seem to be stuck or broken, please let me know, so that I can investigate. I don't review all logs in general, it's beyond my capacity. Thanks for understanding. Regards Jan On Thu, 21 Sept 2023 at 20:46, Jan Šťastný <[email protected]> wrote: > Hello again, > > docker-compose problem has been fixed already. > > There has been almost successful run of a PR check for drools at > https://ci-builds.apache.org/job/KIE/job/drools/job/main/job/pullrequest_jobs/job/drools-pr/view/change-requests/job/PR-5530/4/ > . There's a single failing test, coming from incubator-kie-kogito-examples, > giving it another run to see if repeatable failure (and validate overall > setup). Consider that this is a full-downstream build (FDB) using > buildchain tool, covering drools, kogito-runtimes, kogito-apps, > kogito-examples (all prefixed incubator-kie of course). Execution time over > 5 hours is not so tempting though. > > The reason to run a FDB as default PR check is coming from necessary > migration to Github Branch Source Plugin, which out of the box does not > support custom triggers (like we had previously using comments, etc). This > might be a longer task, but I fully understand the need for a similar > solution. > > I've also progressed with nightly builds, for now without a SNAPSHOT > deployment to nexus. Triggers are not yet enabled, triggering manually > during the testing phase. Given that we already run buildchain in the PR > checks, it seems there will be similar results in the nightly builds. For > now I'm targeting only the default environment for nightlies and will > extend that gradually to the full set we had previously. > > Work on release pipelines has not yet started. > > Regards > Jan > > On Thu, 21 Sept 2023 at 10:17, Jan Šťastný <[email protected]> wrote: > >> Hello, >> I am seeing 2 issues in Jenkins PR checks at the moment: >> * docker-compose failing, reported and fixing as >> https://github.com/kiegroup/kie-issues/issues/584 >> * port conflicts in a few tests - investigating quarkus app startup >> issues, it will be linked to using the host docker network. Might require >> refactoring of the tests, but should be easier than finding another way >> around the docker networking issue we had earlier. >> >> Regards Jan >> >> On Wed, 20 Sept 2023 at 20:27, Spolti <[email protected]> wrote: >> >>> It is not working for kogito-examples as well: >>> https://github.com/apache/incubator-kie-kogito-examples/pull/1778 >>> >>> Em qua., 20 de set. de 2023 às 15:19, ricardo zanini fernandes < >>> [email protected]> escreveu: >>> >>> > Jan, >>> > >>> > Sorry to be a PITA, but it's not working for me. See: >>> > >>> > >>> https://github.com/apache/incubator-kie-kogito-serverless-operator/actions/runs/6252529768 >>> > >>> > The action doesn't even start. >>> > >>> > Cheers! >>> > -- >>> > Ricardo Zanini Fernandes >>> > Vida longa e próspera. >>> > >>> > >>> > On Wed, Sep 20, 2023 at 1:22 PM Jan Šťastný <[email protected]> >>> wrote: >>> > >>> > > 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 >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> >>> >>> -- >>> Regards, >>> --Filippe >>> >>
