You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2022/11/11 16:40:25 UTC
[sling-tooling-jenkins] 01/01: SLING-11673 - Jenkins sanity check stage executed even when no parallel builds are triggered
This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch feature/SLING-11673
in repository https://gitbox.apache.org/repos/asf/sling-tooling-jenkins.git
commit fe29de416641565fe8d87d629b894a8b4824123e
Author: Robert Munteanu <ro...@apache.org>
AuthorDate: Fri Nov 11 17:39:57 2022 +0100
SLING-11673 - Jenkins sanity check stage executed even when no parallel builds are triggered
Correct the stepsMap size check
---
vars/slingOsgiBundleBuild.groovy | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index 2754d16..7018b6c 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -97,7 +97,8 @@ def call(Map params = [:]) {
}
// do a quick sanity check first without tests if multiple parallel builds are required
- if ( stepsMap.size() > 1 ) {
+ // the stepsMap has at least one entry due to the failFast entry
+ if ( stepsMap.size() > 2 ) {
node(globalConfig.mainNodeLabel) {
stage("Sanity Check") {
checkout scm