Hi all, Thanks for so many responses. I'm currently looking into filefingerprinting an copy artifacts plugin. It sounds like the right way, and I can almost get it to work. ;-) but... I'm stuck with the problem that the project referes it at ..\..\debug, while the jenkins output is different, and i need to make sure the compiled dll, is in the path, so it will 'link' correctly in jenkins builds... how should i fix that ?
On Thursday, September 6, 2012 9:15:38 PM UTC+2, Kenneth 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 > > >
