| Re: [papyrus-rt-dev] Nightly builds have failed |
Hi,
I did trigger a new build : https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-nightly-PublishTo-nightly/498/
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Peter Cigéhn
Envoyé : mercredi 9 décembre 2015 09:31
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Nightly builds have failed
Hi,
Thank's Remi! That sounds really nice...
Do you have the possibility to manually trigger the code-gen nightly build as well? The change I was trying to check was in the Xtext stuff for the textual notation that Ernesto have made, and that is only included in the output from the code-gen nightly build, not from the master-all build.
/Peter Cigéhn
On 9 December 2015 at 09:25, SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:
Thanks to Benoit, I made a small update on the build. The Master-ALL will check the git server updates every 15 minutes rather than every hour. I made a mistake on the timer grammar.
Masster-All was a success, you should have access to the latest version.
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de SCHNEKENBURGER Remi 211865
Envoyé : mercredi 9 décembre 2015 09:09
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [papyrus-rt-dev] Nightly builds have failed
Hi,
I retriggered a build on Master-all, to check if the issue has disappeared. I could run some build this morning on the gerrit job, so this should be OK. RT-Master-All is checking updates on the gerrit every 15 minutes on the branch master. If nothing changed, a build is not triggered.
I will let Ernesto or some other guys from the runtime / generator to answer the last question.
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Peter Cigéhn
Envoyé : mercredi 9 décembre 2015 09:03
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Nightly builds have failed
Hi,
I was trying to check the fixes that Ernesto pushed yesterday, that should fix some of the Bugzillas I had written. But to my surprise, I could not see any difference. I then checked Hudson and it looks like there are several builds that have failed during the night:
and also
They seem to both have failed due to failed downloads from other repos and similar.
Since the former build is only run once every 24 hours, I would appreciate if someone could trigger a manual build to see if it works better. It would be good if the master build could be triggered as well. But hopefully there will be a push to master which will trigger it anyway.
I would also like to take the opportunity to ask if we can run these jobs a bit more frequent. I find it a bit frustrating sometimes to have to wait for up to an hour to be able to test fixes. I do know that the Papyrus builds are run each 20 minutes (if something has been pushed). So when I and Camille worked with improving the import tool, we had a very quick turn-around loop with those builds every 20 minutes.
So I wonder what are the reasons for *not* running these builds a bit more frequent to avoid unnecessary waiting time in the feedback loop? If we have capacity in the build server, it should be able to build 20 minutes after something has been pushed to master. Why is the nightly for the code-generator/run-time only run every 24 hours? Yes, it is traditionally called "nightly builds", but for me it was long time ago that "nightly builds" actually were run only once every night. :)
/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
_______________________________________________
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
