You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/09/21 15:16:00 UTC

[jira] [Updated] (SLING-9948) Jenkins: Parallelize steps of pipeline

     [ https://issues.apache.org/jira/browse/SLING-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-9948:
-----------------------------------
    Description: 
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....

  was:
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 https://issues.apache.org/jira/browse/MRESOLVER-123 or we have to use completely separate Maven repositories....


> Jenkins: Parallelize steps of pipeline
> --------------------------------------
>
>                 Key: SLING-9948
>                 URL: https://issues.apache.org/jira/browse/SLING-9948
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: 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.3.4#803005)