It just launched.
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline/538/
De : cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx>
De la part de LE MENEZ Quentin
Envoyé : jeudi 13 juin 2019 09:01
À : Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [cross-project-issues-dev] eclipse-jarsigner-plugin issues on Jenkins builds
Hi again,
I managed to get a properly signed build. I pushed the aggregator update and am currently waiting on the simrel instance
to validate or not the contribution.
Although, as no job was triggered (apart from the gerrit one) I was wondering if it is in idle or not. If so could you
trigger one last aggregation for Papyrus please ?
Thanks,
Quentin
De :
cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx>
De la part de Quentin Le Menez
Envoyé : jeudi 13 juin 2019 01:53
À : Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Objet : Re: [cross-project-issues-dev] eclipse-jarsigner-plugin issues on Jenkins builds
I have been encountering this issue while building Papyrus the past several hours.
Therefore I might need a continuance for a proper RC2 contribution as it draws quite late (early?) and I have only one build left in me before I'm callling it quits for today. I'll try again in about 7hours when I'm back at the office and
if the simrel has not been closed to contributions.