I had encountered above message while creating build from Jenkins featuring maven.
In maven i had used maven-scm-plugin plugins to checkout/update codebase. I came to know that although i had set correct username and password in plugins configuration, Jenkins User credential overwrites scm authentication provided on plugins configuration or Jenkins is not able to read credential define on maven-scm-plugins. Because if i put pom.xml file from outside .jenkins job directory and hit maven goal mvn scm:checkout or scm:update, it will succeed to do assign goal
Here below is scm plugins implementation in my pom.xml file
<!-- Plugins for source code management -->
Any suggestion there to solve this problem?
Another solution i got is run scm piror to build by defining repo url and credential on jenkins interface but my aim is to get it done from maven(pom.xml).
As far as I know your solution is the only solution - you need to run at least one Subversion command from the Jenkins builds slave and supply the Subversion credentials when asked before you can perform builds through Jenkins on that build slave.
One thought: you could try coping the Subversion credential store from a PC where you have already logged into the Subversion server to the Jenkins build slave.