There are a couple of plugins you might use: * Copy Artifacts Plugin: This will copy artifacts from Build "A" to Build "B". * You can set Jenkins up to trigger one build from another. There are two places where this can be done. One is an option to trigger the job when another job finishes. That's right above the option to use your SCM to trigger a build. The other is a post build action to trigger another build. The end result is the same.
Let Build "A" that builds foo.dll that Build "B" needs trigger Build "B". Use the Copy Artifacts plugin to copy the foo.dll from Build "A" to Build "B". Problem solved. It is possible to use a Maven repository combined with Ant and Ivy to store DLLs in your local Maven repository and fetch them as required. It's a hack, but I've seen it work. On Sep 6, 2012, at 3:15 PM, Kenneth <[email protected]> wrote: > I am quite new to Jenkins, and am faling in love ;-) (with him sound wrong > though) > > Anyway I am trying to figure out how to handle projects that depends on each > other. I would really like to only have one job for each project. How should > I handle that one project relies on another? a.exe uses b.dll, b is build > when its the source changes, and a builds when its source change or b i > build... > > I can ofcause place the binaries in a folder, and refer it from a's job, but > there must be a smarter way. > The same problem appears with my unit test projects, that I make as seperate > dll's > > (I am using microsoft VC++ and C# and have subversion as my scm) > > Any tips anyone? > thanks > Kenneth > >
