Peass creates a unique folder for each job, which saves cached data like regression test results and old measurement and RCA results. Therefore, starting builds of the same job in parallel is not possible.
One workaround is to add options { disableConcurrentBuilds() } to builds. Since this requires manual effort by the user and also disables the parallel execution of other plugins (e.g. code quality checks that run before Peass might be assumed to run in parallel), this is not a very nice solution.
Therefore, Peass should create a file .inUse in its temporary folder and wait with a job as long as .inUse is present.
What feature do you want to see added?
Peass creates a unique folder for each job, which saves cached data like regression test results and old measurement and RCA results. Therefore, starting builds of the same job in parallel is not possible.
One workaround is to add
options { disableConcurrentBuilds() }
to builds. Since this requires manual effort by the user and also disables the parallel execution of other plugins (e.g. code quality checks that run before Peass might be assumed to run in parallel), this is not a very nice solution.Therefore, Peass should create a file
.inUse
in its temporary folder and wait with a job as long as.inUse
is present.Upstream changes
No response