CAMEL-24318 - use Maven parallelization for compilation part of Jbang IT tests on Jenkins

[apupier]

tested with
https://ci-builds.apache.org/job/Camel/job/Camel%20Jbang%20IT%20Tests/job/main/537/

it allows to reduce the part of this build from 1h32min to 37min

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

AI-assisted contributions

• If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., Co-authored-by trailers) and the PR description identifies the AI tool used.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[gnodet]

Review Summary

Clean, well-validated CI optimization that adds Maven parallel builds (-T1C) to the compilation-only step of the JBang IT test pipeline.

Verification

• The same approach was already merged for Jenkinsfile.deploy (commit 134d11dd4f3) under the same JIRA ticket, reducing that build from ~3 hours to 25 minutes
• The author validated this change on the actual Jenkins CI infrastructure (build #537) — compilation time improved from 1h32min to 37min
• The -T1C flag is correctly scoped to only the -Dquickly compilation step (line 65), leaving the actual JBang IT test invocations (lines 66-67) sequential to avoid test interference
• The -Dquickly profile skips tests and non-essential plugins, making it a safe candidate for parallelization

---

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

Claude Code on behalf of @gnodet