ederign commented on issue #821: URL: https://github.com/apache/incubator-kie-issues/issues/821#issuecomment-1896206199
@rodrigonull, I was discussing this with Tiago and later with Zanini, and we believe that we should also expand the scope of this task to cover SWF CLI (kn-plugin workflow package). Currently, kn-plugin-workflow has the following internal dependencies: - [go.mod](https://github.com/apache/incubator-kie-tools/blob/c6eb6aa160b54882749a18a39b53059b53424f8e/packages/kn-plugin-workflow/go.mod#L10C69-L10C69) with source dependency to kogito-serverless-operator - [env/index.js](https://github.com/apache/incubator-kie-tools/blob/main/packages/kn-plugin-workflow/env/index.js) dependencies to: 1. [kogito-version](https://github.com/apache/incubator-kie-tools/blob/main/packages/kn-plugin-workflow/env/index.js#L47): your proposal already covers it via runtime release and is used on our pom.xml file of the generated project; 2. [dev mode image deploy](https://github.com/apache/incubator-kie-tools/blob/main/packages/kn-plugin-workflow/env/index.js#L42): used on docker runs for 'non-java' serverless workflow projects I want to check with you if it's possible to include the following requirements on each weekly job execution: - create a new tag on [incubator-kie-kogito-serverless-operator](https://github.com/apache/incubator-kie-kogito-serverless-operator/) to source consumption via go build; - build and deploy a new [dev mode image](http://on%20each%20weekly%20job%20execution/) for the CLI consumption. This standardization is crucial to keep the kie-tools project completely manageable. Is it feasible? /cc @tiagobento @ricardozanini @porcelli -- 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]
