[KOGITO-8351] - Introduce Camel Add-On for Serverless Workflow

[ricardozanini]

Signed-off-by: Ricardo Zanini zanini@redhat.com
See: https://issues.redhat.com/browse/KOGITO-8351

In this PR, we introduce a new feature capable of adding Camel routes in Serverless Workflow projects and call them using the workflow DSL.

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

• You have read the contributors guide
• Your code is properly formatted according to this configuration
• Pull Request title is properly formatted: KOGITO-XYZ Subject
• Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
• Pull Request contains link to the JIRA issue
• Pull Request contains link to any dependent or related Pull Request
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request checks
  Please add comment: Jenkins retest this

• for a specific pull request check
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests

• for quarkus branch checks
  Run checks against Quarkus current used branch
  Please add comment: Jenkins run quarkus-branch

• for a quarkus branch specific check
  Run checks against Quarkus current used branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

• for quarkus main checks
  Run checks against Quarkus main branch
  Please add comment: Jenkins run quarkus-main

• for a specific quarkus main check
  Run checks against Quarkus main branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

• for quarkus lts checks
  Run checks against Quarkus lts branch
  Please add comment: Jenkins run quarkus-lts

• for a specific quarkus lts check
  Run checks against Quarkus lts branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

• for native checks
  Run native checks
  Please add comment: Jenkins run native

• for a specific native check
  Run native checks
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native

• for mandrel checks
  Run native checks against Mandrel image
  Please add comment: Jenkins run mandrel

• for a specific mandrel check
  Run native checks against Mandrel image
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel

• for mandrel lts checks
  Run native checks against Mandrel image and quarkus lts branch
  Please add comment: Jenkins run mandrel-lts

• for a specific mandrel lts check
  Run native checks against Mandrel image and quarkus lts branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel-lts

• Full Kogito testing (with cloud images and operator BDD testing)
  Please add comment: Jenkins run BDD
  This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

[ricardozanini]

See: https://issues.redhat.com/browse/KOGITO-8354

[fjtirado]

Looks good, but we can save some code

[cristianonicolai]

@ricardozanini nice work!
Im just thinking about the version alignment. DO we know if our Quarkus upgrade script will pick the upgrade or is it something we will need to do manually? @radtriste FYI

[radtriste]

Im just thinking about the version alignment. DO we know if our Quarkus upgrade script will pick the upgrade or is it something we will need to do manually?

I believe our script will update it automatically based on the Quarkus platform BOM, right @radtriste?

Our scripts will not if the version is not in the io.quarkus:quarkus-bom

[ricardozanini]

io.quarkus:quarkus-bom

It's not there. So we will have to fetch from their platform? Honestly, I can remove this version since we only needed it because of the Camel DSL XSD.

[ricardozanini]

@radtriste I've removed the Camel version. Now we can rely only on Camel Quarkus. I'll fix the example as well.

[ricardozanini]

jenkins rerun kogito-runtimes tests

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

82.5% Coverage
0.0% Duplication

[radtriste]

lgtm