Hi,
> Newbie here looking to use jenkins to manage our build process. I'm
> attempting to follow jenkins best practices. One specific thing I'm
> wondering is how to set up my build dependencies or pipeline. We have a
> layered architecture which consists of many libraries (around 20) and a
Hi,
Am 17.11.2015 um 15:14 schrieb John Mellor:
>> Typically I don't declare any job dependencies there. Each project can be
>> built and tested on its own, and the projects using the libraries would use
>> the results from the last successful build, so you still get the maximum
>> coverage
he work just
done.
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Simon Richter
Sent: November-15-15 11:14
To: jenkinsci-users@googlegroups.com
Subject: Re: Manage lib dependencies as compilation or link time dependenci
Matt, compile and link time "dependencies" are typically in your make file,
visual studio, eclipse, other IDEs. So the first steps in your build will be to
run these. You don't need multiple jobs. For a simple approach you would just
create a free-style project that 1. Pulls the sources from
