Jenkins dropped our project hierarchies

[Tom Zeller]

Here are options to repair the broken project hierarchies in Jenkins :

1. Deploy snapshots after every commit.
2. Implement a build pipeline.
3. Manually construct project hierarchies.

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.

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.

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.

Okay ?



On Mon, Mar 25, 2013 at 8:21 PM, Tom Zeller <tzeller at dragonacea.biz> wrote:
> For some reason, Jenkins seems to have lost the upstream and
> downstream project hierarchies. There is a possibly related bug, which
> is fixed in a newer version of Jenkins. I guess this broke when I last
> upgraded, not sure.
>
> The upshot is that a change in an upstream project will not trigger
> downstream projects to build.
>
> Thanks Ian for the heads-up.