[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"

[joachim.h...@gmx.de (JIRA)]

Title: Message Title

Joachim Herb commented on JENKINS-31455   Re: Build instability with "ISVNAuthentication provider did not provide credentials" Unfortunately, I cannot confirm that downgrading to version 2.5 of the subversion plugin fixes the problem: I still see it (nearly) every second build in pipeline jobs: The checkout of the external SVN project fails with the authentication error. The external project is hosted on the same SVN server as the base project and the same username/password combination is used for the external project as for the base project. No realm is specified in the pipeline job configuration, but the checkout is done within a groovy pipeline script using the following code: checkout scm: [ $class: 'SubversionSCM', locations: [[ remote: "https://some.server/xxx/", local: 'yyy', credentialsId: credentialsId, depthOption: 'files', depthOption: 'infinity', ignoreExternalsOption: false ]], workspaceUpdater: [ $class: 'UpdateUpdater' ] ] The variable credentialsId contains contains the ID from https://jenkins.server/credentials/store/system/domain/_/credential/ (Credentials) I also tested if a loop around the checkout commands with a number of retries and a delay between them helps, but also not. Only "replay"ing the same job fixes the problem (temporarily). So a workaround would be to catch the checkout exception in the Jenkinsfile and restart/trigger the same job with the same parameters again. Is there a simple way for this (especially reuse the same parameters)? Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.