[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Papyrus-RT-Master-Product timer triggered build fails every morning
|
This, at least, is a known limitation of the "join" plug-in that triggers the Product build.
We had for a long time a problem wherein Product builds ran twice for every change in the Core build, because Core triggered Codegen and Tooling and both of these triggered Product. So, always a redundant Product build. This is fixed by the Join plug-in, which is configured on the Core build to trigger Codegen and Tooling in parallel and then Product. But this plug-in is not smart enough to trigger Product on a self-triggered Tooling or Codegen build.
Configuring the Tooling and Codegen builds to trigger Product would result in three Product builds for every Core build.
I don't know what the solution is within the available Hudson technology.
Cheers,
Christian
On Jan 19, 2017, 04:57 -0500, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi again,
And if someone looks into this, maybe it is good to take a look at why the tooling build does not trigger the product build. Ansgar merged a change related to tooling which triggered build #367 of tooling:
But this in its turn did not trigger any build of Papyrus-RT-Master-Product. So now I probably have to trigger that manual to be able to check the merged change. Or wait for the time triggered build tomorrow, which will fail anyway as indicated below, and then I will have to trigger a manual build anyway! :)
/Peter Cigéhn
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev