snippetMinor
How to mark a step as failed or unstable on timeout, instead of aborting build?
Viewed 0 times
unstableabortingtimeoutinsteadstepfailedhowbuildmark
Problem
I have a stage in my Jenkins declarative pipeline that looks like:
The timeout activates if my tests don't output anything to the console for 5 minutes, and subsequent stages still execute, which is what I want. However, the build is still marked as aborted instead of failed, which I thought the
How do I catch a timeout and mark the build as unstable or failed, instead of aborted?
stage('Step Tests') {
steps {
dir('test') {
catchError(catchInterruptions: true, buildResult: 'FAILURE') {
timeout(time: 5, unit: 'MINUTES', activity: true) {
sh "yarn step-tests"
}
}
}
}
}The timeout activates if my tests don't output anything to the console for 5 minutes, and subsequent stages still execute, which is what I want. However, the build is still marked as aborted instead of failed, which I thought the
buildResult parameter was for.How do I catch a timeout and mark the build as unstable or failed, instead of aborted?
Solution
I've done something similar to this in the past:
I haven't tested this code exactly as I wrote it here, so think of this more as a kind of rough sketch rather than polished final product.
stage('Step Tests') {
steps {
dir('test') {
script {
try {
timeout(time: 5, unit: 'MINUTES', activity: true) {
sh "yarn step-tests"
}
} catch (Exception e) {
currentBuild.result = 'FAILURE'
}
}
}
}
}I haven't tested this code exactly as I wrote it here, so think of this more as a kind of rough sketch rather than polished final product.
Code Snippets
stage('Step Tests') {
steps {
dir('test') {
script {
try {
timeout(time: 5, unit: 'MINUTES', activity: true) {
sh "yarn step-tests"
}
} catch (Exception e) {
currentBuild.result = 'FAILURE'
}
}
}
}
}Context
StackExchange DevOps Q#9679, answer score: 4
Revisions (0)
No revisions yet.