| We have implemented something called `retryWithPrompt` to avoid sudden failures on long running pipelines like environmental and other known issues. And also we have commands tailing long text before those actually fail, and retries on these steps doesn't guarantee that they would go through this time. This is leaving multiple error steps on the same stage and being those very long text when we initially land on that stage the page is too hard to browse, it would be very nice if we can make this configurable or make it default similar to other steps, like in progress step. Exampl
e:
node('LINUX') {
writeFile file: 'test.sh', text: "for i in {1..500}; do echo -n 'Loop \$i'; date ; sleep 1; done; exit 1"
waitUntil {
try {
sh 'chmod +x test.sh'
sh './test.sh'
return true
}
catch(e) {
println "Error: ${e}"
println "StackTrace: ${e.getStackTrace()}"
def userInput
timeout(900) {
userInput = input(id: 'userInput', message: "Retry? or Ignore", parameters: [[$class: 'ChoiceParameterDefinition', choices: "Retry\nIgnore\n", description: 'Select...', name: 'Select...']])
}
echo "User Selected: " + userInput.toString()
return userInput == 'Ignore'
}
}
}
The above code is just an example and which will allow users to retry number of times and error steps are so many in there and those are too long, the default behavior is expanding those lines, which is causing a lot of confusion. appreciate your help. Find the attached screenshots. for the sample output. Thanks again for the consideration. |
