aboutsummaryrefslogtreecommitdiffstats
path: root/server/sonar-vsts/yarn.lock
diff options
context:
space:
mode:
authorEvgeny Mandrikov <138671+Godin@users.noreply.github.com>2019-07-26 14:50:36 +0200
committerSonarTech <sonartech@sonarsource.com>2019-07-26 20:21:46 +0200
commit6fa9cf49b78f8f49b300890e57398247163a66b1 (patch)
treeacadc32832090da7f8bf6bd8245d686aba471a8d /server/sonar-vsts/yarn.lock
parent43d710e93b5bbe96e5364e9eb5dc7c88b2a2118c (diff)
downloadsonarqube-6fa9cf49b78f8f49b300890e57398247163a66b1.tar.gz
sonarqube-6fa9cf49b78f8f49b300890e57398247163a66b1.zip
Usage of Gradle option "--parallel" should be safe
Gradle should not execute several "yarn install" in parallel, because Yarn doesn't support concurrent access to its global cache. "task1.mustRunAfter(task2)" ordering has an effect only when both tasks are scheduled for execution, however currently task ":private:docs:yarn" is not executed during execution of "gradle build". Therefore "mustRunAfter" should be established between all pairs of "yarn install" tasks to define their total order and to prevent their concurrent execution even in case when one or more of these tasks not scheduled.
Diffstat (limited to 'server/sonar-vsts/yarn.lock')
0 files changed, 0 insertions, 0 deletions