tiagobento opened a new pull request, #2041:
URL: https://github.com/apache/incubator-kie-kogito-apps/pull/2041

   Due to the fact that for the Apache release we'll need a buildable zip that 
produces all artifacts necessary for downstream repos, combined with the usage 
the native binaries of JIT Executor have on `kie-tools`, the publication method 
needed to change from an external GitHub Actions workflow publishing to NPM to 
Maven modules that are part of the build of this repo.
   
   This change introduces a new profile "jitexecutor-native" that will, 
depending on the OS, include a specific <module>. This is necessary because 
native compilation does not support cross-compilation, so we need to run three 
separate jobs, publishing three separate artifacts, each containing the binary 
targeting an OS.
   
   The configurations were taken from `jitexecutor-runner` and replicated 
through the new OS-specific modules. We have tested this on @ljmotta's fork. 
See 
https://github.com/ljmotta/incubator-kie-kogito-apps/actions/runs/8993866752.
   
   The release Jenkins job will still be responsible for publishing all the 
Maven modules in this repository, however, for `jitexecutor-native`, we need to 
rely on the GitHub Actions workflow, since we need binaries for macOS and 
Windows too. Both unsupported on Apache Jenkins' infrastructure.
   
   @rodrigonull We haven't completed the changes to 
`publish-jitexecutor-native.yml`, since we don't know how to properly configure 
the Maven publication, especially with the custom classifier. Can you help us? 
We believe that the second `mvn clean install` for each OS should be changed to 
`mvn clean deploy` with the proper configuration, but we're not sure.
   
   The new module `jitexecutor-native` is only included if the profile 
`jitexecutor-native` is explicitly set with `-P`.
   


-- 
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]

Reply via email to