Re: [papyrus-rt-dev] Papyrus-RT-Master-Product timer triggered build fai

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

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:

https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-Tooling/367/

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

On 19 January 2017 at 10:29, Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

If you check the build history of Papyrus-RT-Master-Product

https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-Product/

you can see that it for the last few days, since January 15th, always fails in the build triggered by a timer, i.e. build #335, #333, #329, #324, and #322. All these builds have been triggered by upstream build of tooling and core, where it is the core build that is started by a timer.

When checking the logs, it looks like all of these builds have failed with the following

Caused by: org.apache.maven.plugin.MojoFailureException: Installation of product org.eclipse.papyrusrt.rcp.product for environment win32/win32/x86_64 failed

I have manually re-triggered a new build a few times, which then succeeds.

Can someone with some more insight check what it is that causes these builds to fail so consistently?

/Peter Cigéhn