apupier opened a new pull request, #8941:
URL: https://github.com/apache/camel-quarkus/pull/8941
locally the deploy with `./mvnw -B -e -ntp -Ddeploy -Dquickly clean deploy
-DaltDeploymentRepository=your_repo_id::default::file:/tmp/alt-repo-quarkus`
takes 21 minutes
and with the -T1C `./mvnw -T1C -B -e -ntp -Ddeploy -Dquickly clean
deploy
-DaltDeploymentRepository=your_repo_id::default::file:/tmp/alt-repo-quarkus` it
takes 7 minutes
On CI, the job is currently taking 3 hours. So expecting to at least divide
by 2.
for Sonar, use it only for the compilation part, not the sonarscanner which
doesn't support the parallelization. tried on CI
https://ci-builds.apache.org/job/Camel/job/Camel%20Quarkus%20Sonarcloud%20Deploy/job/main/1144/
, it allowed to go from 25 minutes to 14 minutes
<!-- Uncomment and fill this section if your PR is not trivial
[ ] An issue should be filed for the change unless this is a trivial change
(fixing a typo or similar). One issue should ideally be fixed by not more than
one commit and the other way round, each commit should fix just one issue,
without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly
spelled subject line and body. Copying the title of the associated issue is
typically enough. Please include the issue number in the commit message
prefixed by #.
[ ] The pull request description should explain what the pull request does,
how, and why. If the info is available in the associated issue or some other
external document, a link is enough.
[ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close
the named issue upon merging the pull request. Using them is typically a good
idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if
necessary) before sending the pull request.
[ ] Contributor guide is your good friend:
https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
-->
--
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]
