*Jobs*

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

All jobs should be launched by our pipeline.
Testing Camel with jbossqe-camel-it presentation
Camel test suite guideline

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

All jobs are quite stable, eap-camel-components usually needs some rerunning
More details here - https://docs.google.com/document/d/1UFoGQ6aPipHPlfTO7G_CWWO4aUR3bw4MYfDsLwdqy_M/edit#heading=h.6fmkeh2hyf3c

[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'

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