Jenkins dropped our project hierarchies

[Cantor, Scott]

On 4/1/13 8:51 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>For now, I suggest deploying snapshots after every commit (1). I
>though this was too frequent, but it appears to be the path of least
>resistance.

Does seem a bit excessive.

>The problem seems to be the multiple upstream parent jobs. I added
>nightly jobs which deploy snapshots because I thought deploying a
>snapshot after every commit was too frequent. The
>java-parent-project-v3-nightly job seems to conflict with
>java-parent-project-v3 when Jenkins automagically constructs the
>project hierarchy.

Probably not just the parent project, though? If that was the only
problem, I'd say let's just manually deploy changes to that particular
artifact since it won't change as often.

>I think that manually constructing project hierarchies (3) is not a
>good idea, and implementing a build pipeline (2) is interesting but
>will take some time.

Is 3 really that hard or does it operate at the level of each module
within the multi-module projects? At the top level, it's a pretty simple
hierarchy.

-- Scott