*Jobs*

• https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.12-eap-camel-architecture/ - owner bsmolice
• https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.12-eap-camel-components/ - owner bsmolice
• https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.12-eap-camel-components-unstable/ - owner bsmolice
• https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.12-eap-camel-eip/ - owner bsmolice
• https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.12-eap-camel-scenarios/ - owner bsmolice

All jobs should be launched by our pipeline.
Camel test suite guideline

It is possible also to emulate pipeline using fuse-workspace project

[example]
Double-check and eventually properly set in 'job.eap.url' and 'job.eap.fuse.installer.url' in 'env.properties'
run 'tools/jj run eip-camel-eap -Djob.mvn.properties=rerunTestCount=0,version.camel=2.23.2.fuse-7_10_0-00020-redhat-00001,version.redhat.fuse=7.10.0.fuse-sb2-7_10_0-00014-redhat-00001,version.springboot=2.3.12.RELEASE'

NB: some tests may use testcontainers. In order to run those locally with podman you need to:
1. start podman as a service: 'podman system service -t 0 tcp:localhost:8880 &'
2. export the following env variables:
export DOCKER_HOST=tcp://localhost:8880
export TESTCONTAINERS_RYUK_DISABLED=true

In order to check failures you can run 'grep -REi "<failures>[1-9].*" --include failsafe-summary.xml'

All jobs are quite stable, eap-camel-components might need some rerunning