Forum Discussion
garfield19
12 years agoNew Contributor
redfish4ktc wrote:
so you have the following solutions
- in your pom, add the soapui repository (this is what is documented in soapui documentation but this is not the best choice)
- in the settings.xml file used by jenkins, add the soapui repository
- configure your company nexus instance to mirror soapui repository and make this mirrored repo available as others repository. This is the best solution (see http://www.sonatype.com/people/2009/02/ ... -bad-idea/)
with all these solutions, maven will be able to download dependencies as usual!
You were absolutely right. It was resolved after I pointed it out to the admin, and they modified the nexus instance to have all the repo of soapui. So it was a happy ending for me after all. In all fairness, this being my first foray into Jenkins, I did have a good learning experience throughout this hiccup.
question: if it works on your dev machine, you have already done something like this before, no?
I created a local instance on my personal laptop.. as I was toying around Jenkins for the first time. And hence there was no blocking whatsoever for the external portals where the poms and jars were downloaded by Jenkins. Unfortunately, in the nexus, there is no option to download it so. And hence without much effort from my end, it had worked on my machine.
Related Content
- 8 years ago
- 9 years ago
Recent Discussions
- 15 years ago