Folks; we use Jenkins all along with a local Apache Archiva maven repository to build maven projects. There's a dedicated user for Jenkins to access the repository and download (and deploy) artifacts. The user has all the required permissions, but I fail to set up maven in Jenkins to work with repo or credentials. Tried to go the usual way (placing a settings.xml in the Jenkins users $HOME/.m2 , even tried the global maven settings.xml). Building with maven from the terminal, things work well, but Jenkins builds fail pretty early because maven gets a 401 trying to download the artifacts off the repository.
So to ask: Is there anything special to think of when using Jenkins with a maven repo that requires authentication? Where to put credentials to make Jenkins find these? TIA and all the best, Kristian -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3e9468ad-9d1d-47ae-969e-9624b4c4aa8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
