[
https://issues.apache.org/jira/browse/SLING-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554641#comment-17554641
]
Konrad Windszus commented on SLING-9948:
----------------------------------------
Fixed in
https://github.com/apache/sling-tooling-jenkins/commit/3782cb94c511db8693306ec74d43f678d15d5d0f.
Let us track
bq. I think we should also restrict branch builds to master only. If we submit
PRs from branches of the same repo, Jenkins runs two jobs.
separately.
> Jenkins: Parallelize steps of pipeline
> --------------------------------------
>
> Key: SLING-9948
> URL: https://issues.apache.org/jira/browse/SLING-9948
> Project: Sling
> Issue Type: Improvement
> Components: Build and Source Control
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> We should improve the speed of Jenkins pipelines by executing multiple Maven
> builds in parallel.
> Also the Sonarqube step executes the Maven build again, instead it should
> reuse the workspace of a previous build instead.
> Parallelizing Maven probably requires MRESOLVER-123 or we have to use
> completely separate Maven repositories....
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
