Yes, we actually do generate (one single) metadata file during the main
build job, this metadata is archived, and passed through the whole
pipeline, to other downstream jobs, promotion jobs etc. With this
metadata file being fingerprinted, you get a very nice side effect, that
Jenkins can figur
Thanks John, that sounds like a good idea. I'll see what I can do by
way of archiving artifacts. So far, I had been thinking of artifacts
in term of pure build output (files, libraries, whatever), not as
metadata.
On 23 Feb., 23:56, John Vacz
wrote:
> On 23.02.2012 08:36, Sason wrote:
>
>
>
>
>
>
On 23.02.2012 08:36, Sason wrote:
Hi there,
I'd like to set up two dependent build projects for the same software
product as follows:
- have a "quick" build run every time a developer commits changes,
i.e. using the SCM polling trigger. This will only be an incremental
build, followed by unit te
Hi there,
I'd like to set up two dependent build projects for the same software
product as follows:
- have a "quick" build run every time a developer commits changes,
i.e. using the SCM polling trigger. This will only be an incremental
build, followed by unit tests.
- run a scheduled full "nightly
