From b8f34f66d57e4c1c89fa5e0a80088cb1a0432bb5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=8A?= =?UTF-8?q?=D1=80=20=D0=9A=D1=83=D1=80=D1=82=D0=B0=D0=BA=D0=BE=D0=B2?= Date: Mon, 13 Jan 2025 19:12:46 +0200 Subject: [PATCH] Make Jenkins complain on new warnings from the current PR That should prevent the need to manually reset the baseline when new warning is introduced by previous PR or even due to change outside of the project. --- Jenkinsfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Jenkinsfile b/Jenkinsfile index 019ee16d9f..9c09b55761 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -39,7 +39,7 @@ pipeline { repository/target/repository/**') junit '**/target/surefire-reports/*.xml' discoverGitReferenceBuild referenceJob: 'eclipse.pde/master' - recordIssues publishAllIssues: true, tools: [eclipse(name: 'Compiler and API Tools', pattern: '**/target/compilelogs/*.xml'), mavenConsole(), javaDoc()], qualityGates: [[threshold: 1, type: 'NEW', unstable: true]] + recordIssues publishAllIssues: true, ignoreQualityGate: true, tools: [eclipse(name: 'Compiler and API Tools', pattern: '**/target/compilelogs/*.xml'), mavenConsole(), javaDoc()], qualityGates: [[threshold: 1, type: 'NEW', unstable: true]] } } }