Hi, as part of the CI migration to Apache, we found out the Apache GitHub Actions are overloaded and the wait times to start a job may be 6-8 hours (1). This is not currently usable for the development of kie-tools (and other repositories we have using GitHub Actions).
As we started using Apache Jenkins (2) for the runtime repositories, my proposal for kie-tools is this: - Focus only on the initial goals at the start - Basic PR check and daily builds. - Implement the initial goals from the previous point on Apache Jenkins, using Multibranch pipeline (we basically need Jenkinsfiles for the builds). Initial needs: - Basic PR check - A build that will run the bootstrap and build of kie-tools, runs all required tests. This will enable us to say a code change is not breaking anything in the repository. - Daily builds - A daily build done on the main branch of the repository, with deployment of artifacts to appropriate repositories. The main focus of this point will be about where we have to deploy the artifacts and how to deploy it there. We have e.g. the backing infrastructure for sandbox.kie.org etc. running, so things like this would need to be sorted as part of this task. I want to also define as part of this proposal, that anything else apart from these two initial goals is not a focus of the inicial CI migration work. That means that it can be done only after we have the initial goals implemented. This is to make sure we have the core CI for kie-tools ready. The discussion for this proposal will be open till Tuesday, 26th September 2023, 8:00 UTC. Initial exploratory work around this proposal may already be done during this timeframe, with no code around this merged into the main branch, until we have agreement on this topic. I also recommend considering a similar approach for other repositories using GitHub Actions. Best regards, Tibor (1) https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status (2) https://ci-builds.apache.org/job/KIE/
