I keep this conversation here to possibly help other people with a similar question.
---
It's not the only way but it's the cleanest way in my opinion when you have enough artifacts to fill your hard drive.
I think the way you integrate the artifact repository with Jenkins depends on your projects. In a Maven project for example, you can configure your repository in your pom.xml in order to deploy artifacts on it automatically. Then, you can configure Maven to lookout for dependencies in your repository (instead of the default one).
Also, there are some plugins (see
this one) that can help to integrate your repo with Jenkins in various ways.
I'm no expert here but I would definitely go for the artifact repository. However, if you really don't want it, I think you can find the answer to your specific question
here.
Good luck
Thomas
Le 26 mai 2016 à 17:22, <> a écrit :
Hi Thomas
I know why we're running out of disk space, it's a virtual machine and our vm host is quite limited in space so expanding to the degree needed is not possible. However we do have plenty of space on our fileserver, just need to get jenkins to actually leverage it.
I must admit I was hoping for something less than an artifact repository. All we want is for Jenkins to put it's data on our network drive. But if that is the only way I guess we'll have to do that.
How does an artifact repository integrate with Jenkins? Will we be able to list our builds and grab the artifacts directly from Jenkins?
Thanks for your reply
Joen