Ricardo, Eder and Community Members, We definitely need to have a conversation about how best to deal with our repositories and in general the whole codebase organization. I think it's fair to say that it's not working well. We also consume many times more computing resources that we should and we have complex workflows using external CI on top of CI to coordinate such complexity.
With that being said, I don't think this is the right moment to do so. My suggestion is that we find a solution for the current problem and I ack that it might not be a small change. On Thu, Mar 7, 2024 at 12:27 PM ricardo zanini fernandes <[email protected]> wrote: > > Yeah I forgot about the jars now in tools that we need in images. So I > guess the solution is to move everythign to one single monorepo. That might > be really tough to handle in the long run. > > I hope I can learn how to pull specific folders from the monorepo then. 😅 > > -- > Ricardo Zanini Fernandes > Vida longa e próspera. > > > On Thu, 7 Mar 2024 at 1:33 PM Eder Ignatowicz <[email protected]> wrote: > > > Zanini, > > > > On Thu, Mar 7, 2024 at 9:44 AM ricardo zanini fernandes < > > [email protected]> wrote: > > > > > Hi! Apart from the kn-workflow, what else kie-tools depends on the > > images? > > > > > > > Paulo/Caponetto can elaborate more, but remember that in the past, we > > stopped using tools for custom images to use only images from images repo? > > > > Also, what do we do in cases like this one? > > https://github.com/apache/incubator-kie-kogito-images/pull/1734 > > > > My guess is that we will eventually include something from tools in > > an image, and if I understand correctly, operator repo (including > > kn-workflow, images) -> runtimes -> kie-tools will not accommodate that. > > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
