tiagobento commented on PR #2042: URL: https://github.com/apache/incubator-kie-kogito-examples/pull/2042#issuecomment-2596287385
@wmedvede Right... I'm seeing this discussion much more as a generic discussion talking about ALL examples, and the scope of disagreement being mostly targeted towards examples that only depend on the engines, runtimes, and everything coming from drools, optaplanner, kogito-runtimes, and kogito-apps. Since the SonataFlow Operator is already permanently inside KIE Tools, I figured this was an obvious move to do and make everyone's life easier. Yours included. Being realistic, `kogito-examples` building as the last repository of the "build-chain" would force us to double down on using the unmaintained, black-box library that Enrique Cano created in the past (build-chain), while also increasing complexity in the already impossible-to-maintain "Kogito framework" on Apache's Jenkins. I'll most certainly -1 any proposal that involves us burying our codebase in a deeper dependency with these two systems. Having `kogito-examples` at the end of the pipelines would also imply that `kie-tools` wouldn't be the last repo on the chain, adding 3+ hours for every PR on the Apache KIE community, as we wouldn't be able to take advantage of its powerful partial builds mechanism, thus resulting in a massive waste of computational resources in our development operation. You've been contributing to `kie-tools` for the past few months, so I believe you're familiar with the partial and partitioned builds we're able to do on `kie-tools` PR checks, and I'm sure you appreciate the speed with each of your PRs have been automatically checked, reviewed, and merged. Let me know what I'm missing and how moving the SonataFlow Operator examples to `kie-tools` would make things harder for you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
