From 17a0733527624341aae37c91d33402abe6d3867c Mon Sep 17 00:00:00 2001 From: Sebastien Boeuf Date: Fri, 14 Aug 2020 13:58:23 +0200 Subject: [PATCH] Jenkinsfile: Don't retry integration tests on failure We recently added the ability for the gnu and musl workers to retry if integration test were not passing, relying on some simple Jenkins options. Unfortunately, this is not working as expected as the retries never pass either. The suspected reason is the machine itself, which might be scheduled on some specific hardware, which makes our VMs more error prone. Bottom line, on a faulty machine, the tests will always fail, therefore there is no added value in retrying on the same machine. Signed-off-by: Sebastien Boeuf --- Jenkinsfile | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Jenkinsfile b/Jenkinsfile index 06b925de0..5c5e9e483 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -46,9 +46,6 @@ pipeline{ } } stage ('Run integration tests') { - options { - retry(3) - } steps { sh "scripts/dev_cli.sh tests --integration" } @@ -111,9 +108,6 @@ pipeline{ } } stage ('Run integration tests for musl') { - options { - retry(3) - } steps { sh "scripts/dev_cli.sh tests --integration --libc musl" }