On Thu, Sep 6, 2012 at 2: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?
With subversion you can commit the .dll binaries back to the
repository and use svn: externals to pull them into the workspace of
other projects. That works the same with/without jenkins.
--
Les Mikesell
[email protected]
