Hi Thiago, I'll take a look at kn-plugin-workflow: https://github.com/apache/incubator-kie-tools/tree/main/packages/kn-plugin-workflow for 10.0. I had a chat with Jakub Schwan and he should be taking care of the operator.
Do you have an issue reported for the e2e tests that were simply not working? I was not aware of that at all, so any details are appreciated. Thanks! On Mon, 15 Jul 2024 at 17:30, Alex Porcelli <[email protected]> wrote: > Thank you for clarifying, Fabrizio! > > > On Mon, Jul 15, 2024 at 12:24 PM Fabrizio Antonangeli < > [email protected]> wrote: > > > Not in my opinion as sonataflow-operator is a new kie-tools package and > > the bug is only for local developments. > > > > On Mon, 2024-07-15 at 12:16 -0300, Alex Porcelli wrote: > > > Is this something that blocks the release? > > > > > > There’s another thread [1] in ML already planning the release branch… > > > > > > [1] - > > > https://lists.apache.org/thread/g164c2z9y82l3bprmpn132zdwjk2nds8 > > > > > > On Sun, Jul 14, 2024 at 3:16 PM Fabrizio Antonangeli < > > > [email protected]> wrote: > > > > > > > Hi Thiago, > > > > > > > > Just for information, regarding the sonataflow-operator package on > > > > kie-tools, I am working on [1]. I am short of knowledge of this > > > > particular > > > > tech-stack but I'm trying my best to fix this issue asap. > > > > > > > > [1] https://github.com/apache/incubator-kie-tools/issues/2461 > > > > > > > > > > > > On Sat, Jul 13, 2024 at 12:49 AM Thiago Lugli > > > > <[email protected]> > > > > wrote: > > > > > > > > > Following the discussion regarding circular dependencies on > > > > > Apache KIE, > > > > > we’ve migrated most of the Sonataflow packages to kie-tools > > > > > (kogito-swf-builder image – renamed to sonataflow-builder-image, > > > > > kogito-swf-devmode image – renamed to sonataflow-devmode-image, > > > > > kogito-serverless-operator – renamed sonataflow-operator) [1]. > > > > > They are currently building successfully on the kie-tools CI, but > > > > > for the > > > > > sonataflow-operator package we have never actually been able to > > > > > test if > > > > > it’s working correctly, either because there was an unreleased > > > > > dependency > > > > > (e.g. some snapshot build or image) at the time or simply because > > > > > the e2e > > > > > tests were not working on the original kogito-serverless-operator > > > > > repository [2] and I lacked the proper knowledge to fix them. > > > > > > > > > > My question is: Given that the sonataflow-operator and its > > > > > dependencies > > > > > are part of the Apache KIE 10 release, and considering that the > > > > > kogito-serverless-operator repository is not listed as part of > > > > > the > > > > release > > > > > procedure [3], can we ensure that they are functioning as > > > > > expected on > > > > > kie-tools? > > > > > > > > > > The same question is valid for the kn-plugin-workflow, since it > > > > > directly > > > > > depends on the sonataflow-operator. > > > > > > > > > > [1] Packages on kie-tools: > > > > > > > > > > * sonataflow-operator: > > > > > > > > > > > > https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-operator > > > > > * kn-plugin-workflow: > > > > > > > > > > > > https://github.com/apache/incubator-kie-tools/tree/main/packages/kn-plugin-workflow > > > > > * sonataflow-builder-image: > > > > > > > > > > > > https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-builder-image > > > > > * sonataflow-devmode-image: > > > > > > > > > > > > https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-devmode-image > > > > > > > > > > > > > > > [2] kogito-serverless-operator repo: > > > > > https://github.com/apache/incubator-kie-kogito-serverless-operator > > > > > [3] Apache KIE 10 :: Release Procedure: > > > > > > > > > > > > https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit#heading=h.69qvogh2xqsq > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
