In the "build sheriffs" discussion, https://lists.apache.org/thread/h897tdslwmvhv0fb0ovjo0vgf1xwtnx7
Tiago suggested CI/CD improvement -- simplifying and easing. > My opinion is that we could try and concentrate our efforts to reduce > the barrier of entry to maintaining the CI and automations we have, > while putting a system in place that will naturally have each one of > us know at least the basics of how the CI and automations work. I agree that we may need to fully review the jobs/scripts and slim them down. The task may include removing unnecessary jobs and moving a jenkins job to a GHA (when it makes sense). Btw, Such efforts (including discussions) will take a long time. In the meantime, shall we keep fixing kogito-pipelines (and Jenkinsfiles in other repositories) issues? I'm asking because Jan raised a concern: > I'd check one thing here with the mailing list - if we still want to perform any steps towards being part of that platform. I mean, fixing pipelines is a good thing here, but I am not sure if we actually want to make it work. https://github.com/apache/incubator-kie-kogito-pipelines/pull/1229#issuecomment-2268789394 Per my understanding, Jenkins and kogito-pipelines will not completely go away even if we will simplify CI/CD. So it makes sense to fix issues, I think. Please share your thoughts on this. Regards, Toshiya
