Some members of the PPMC got together in a call and were able to discuss the topic more fluidly... after some evaluations of alternatives and trade-offs, here is what has been agreed:
- KIE Tools will move away from GitHub Actions for practical purposes - The KIE Tools repository will be temporarily left in the kiegroup organization - A new temporary repository [1] will be created under the Apache organization to start translating the current GHA automation to Jenkins - Once some automation is in place, the new automation code will be ported to the KIE-Tools repository in kiegroup, and the original KIE-Tools repo will be officially transferred to Apache. Please, members of PPMC, please confirm if I captured it right. Please also let us know if there is any concern about this action. [1] - https://github.com/apache/incubator-kie-tools-temporary-rnd-do-not-use On Thu, Sep 21, 2023 at 8:49 AM Eder Ignatowicz <[email protected]> wrote: > > Thanks Tibor, > > For [1]: If there are not reliable GitHub Actions, we cannot address CVE in > > any way. So to be able to build a release with a CVE fix, we need to have a > > build system capable of doing builds. For that is my proposal, to start > > having that. > > > > Yep. I agree that having a build system is an excellent first step on that. > My concern is that without all our automation to publish releases, the only > suitable option for us would be to do the release manually, which will be a > challenge due to the number of artifacts that we also produce with the > number of different places that we need to release (VS Code store, Chrome > Store, GitHub pages, NPM, etc.) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
