Re: [papyrus-rt-dev] Eclipse Installer errors due to Papyrus

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

Hi Remi. Some comments and questions below.

On Thu, May 26, 2016 at 1:31 PM SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:

Hi Ernesto,

 

I don’t think having this deploy job would change anything to the issue. You are consuming some data which is being changed, and you fall down on the transition time. Results would be the same if you put it on a download area or on the Hudson server.

I think the RC2 build should not impact the nightly builds, so there should not be any consequences here. The only difference may be the higher number of commits on these busy days, so the Papyrus nightly has more transition times.

Right, I think that's the problem, when the developer is installing while one of these transitions is taking place. Christian mentioned this in another thread.

 

 

To tackle these issues of being dependent of nightly bits, one solution would be to depend only on milestones or on released Papyrus(-RT) binaries, as these ones are moving not so often.

That was my main point in the other thread, that if we had something a little more stable, the likelihood of running into this sort of problem would be greatly reduced. But we don't seem to have a nightly for Tooling on Papyrus-RT. The closest is Papyrus-RT-Master-All, which polls the git repo (I'm not certain how often, as I don't understand the syntax */15 * * * * and its description suggests that it would "skip" every 15 minutes). I think that given the number of merges, this might be happening too often.

 

But that would mean that you would not benefit from the latest fixes or improvements of Papyrus, sometimes required for some evolution on Papyrus-RT.

True. But I wonder if perhaps, just to get the development environment up, it might be better to use a stable one which is not the latest, and then if the user really wants the very latest, we could use that. I'm not sure what is best.

 

Maybe the other people in charge of Papyrus or Papyrus-RT would have a different insight here.

 

I would also like to hear what others think.

 

While we are speaking of dependencies, I currently cannot (or prefer not) to merge the stuff around default language framework, because the gerrit-coden is failing in my patch [1]. This is due  to the fact that the cogen build is targeting the nightly builds of Papyrus-RT master all, where my new feature/plugin is still not pushed, as it is being added with the contribution being built on common area (the famous rts uml model plugin…). There could be in this case some more detailed rules on the gerrit trigger to launch or not the gerrit jobs, or the gerrit jobs should be cascading or “smarter”, but I am afraid we are facing a technology issue there. We discussed a bit with Camille about that issue this evening, but we do not see any good solution.

 

I'll respond to this in another thread, since it's a bit of a different issue.

 

Regards,

Rémi

 

[1] https://git.eclipse.org/r/#/c/73509/

 

 

 

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

www.eclipse.org/papyrus

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Ernesto Posse
Envoyé : jeudi 26 mai 2016 18:48
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Eclipse Installer errors due to Papyrus

 

I, and at least one other person, have been getting errors while attempting to install the developer environment and there are errors resolving papyrus bundles.

 

I understand this can happen while the Hudson build is replacing the repos, is this the case?

 

I saw a message on the mdt.papyrus.dev mailing list that they were building RC2 yesterday. Could this be the cause?

 

This reminded me of a message I posted on May 11 ("Tooling Gerrit builds and p2 repo"), asking if we could have more stable p2 repos for the tooling side (an actual nightly) so that we don't have this problem. There was only one response from Peter, but no one from Tooling has responded. Could we create a Hudson job to publish the Core/Profile/Tooling to a nightly repo? (Hopefully Papyrus would do that too)

 

Thanks

 

--

Ernesto Posse

Zeligsoft

 

_______________________________________________
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