The Unified and Autonomous Development Platform
Fix issue #898 - CI/CD should wait for k8s to add node to 0-node pool before failing the job
Robin Shen2845248b5998
diff --git a/server-plugin/server-plugin-executor-kubernetes/src/main/java/io/onedev/server/plugin/executor/kubernetes/KubernetesExecutor.java b/server-plugin/server-plugin-executor-kubernetes/src/main/java/io/onedev/server/plugin/executor/kubernetes/KubernetesExecutor.javaindex 263dcc0de1..2bcd64b052 100644--- a/server-plugin/server-plugin-executor-kubernetes/src/main/java/io/onedev/server/plugin/executor/kubernetes/KubernetesExecutor.java+++ b/server-plugin/server-plugin-executor-kubernetes/src/main/java/io/onedev/server/plugin/executor/kubernetes/KubernetesExecutor.java@@ -393,7 +393,8 @@ public class KubernetesExecutor extends JobExecutor implements Testable<TestDataif (!osInfos.isEmpty()) {return OsInfo.getBaseline(osInfos);} else {- throw new ExplicitException("No applicable working nodes found");+ jobLogger.warning("No matching nodes found, assuming baseline os as amd64 linux");+ return new OsInfo("Linux", "", "amd64");}}