I also think using the fingerprint plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint) will be very useful
to track dependencies - i.e. this build failed because these dependencies are
not compatible...
*pretty cheap
Another problem caused by not using the "Block build when upstream project is
building" or "Block build when downstream project is building" in my post setup
is that Job A and Job B could end up running on the same slave. This would be
problematic (for me at least) since the artefacts of Job A
I'm also new here - but possibly facing similar problems (C#). I'm not sure
how exactly you expect the dependencies to be "handled", but I thought I would
post my opinion.
I am going for your option B "one job for each project?"
My current plan is to add "build other project" "post build tasks
I'm a beginner so just putting my opinion out there. You could use a single
job if all the code repository is the same. This way you won't have to move
artifacts around much.
OR
Whichever projects are directly interdependent (those that require the
other's binarys) - combine them in one job, k
http://stackoverflow.com/questions/7555883/using-nuget-with-visual-studio-2005
looks
like someone got it to work, kinda.
Before I had NuGet implemented, I use the artifact copy plugin to copy the
dll's to the right directories for it to compile. (bin/Debug or something
like that).
On Mon, Oct 8,
It sounds good, but appearntly NuGet doesn't support Visual Studio 2005. ;-(
Den mandag den 8. oktober 2012 16.06.06 UTC+2 skrev Larry Shatzer, Jr.:
> I use one job per project, and use NuGet (http://nuget.org/) to store
> artifacts and depend on them. There is no auto dependency feature for
>
Kenneth wrote:
> I'm trying to setup jenkins to monitor a solution with C++ and C# in multiple
> solutions, but in one repository.
> (VS 2005 and .NET 2.0)
>
> How should I configure jenkins to build and test it?
>
> my suggested alternatives are:
> a) one job for each solution? - rather larg
I use one job per project, and use NuGet (http://nuget.org/) to store
artifacts and depend on them. There is no auto dependency feature for
triggering dependency jobs. I've manually set them up.
On Mon, Oct 8, 2012 at 12:33 AM, Kenneth wrote:
> I'm trying to setup jenkins to monitor a solution wi
I'm trying to setup jenkins to monitor a solution with C++ and C# in
multiple solutions, but in one repository.
(VS 2005 and .NET 2.0)
How should I configure jenkins to build and test it?
my suggested alternatives are:
a) one job for each solution? - rather large jobs
b) one job for each proje
Hi Guru's
I am configuring jenkins for the first time on a C# and C++ solution, with
multiple projects.
I have some projects depending on other projects, how do I set jenkin up so
it will build projects when projects they use change?
(without haveing to make a jenkins job contain all projects.)
11 matches
Mail list logo
