Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Nightly build repos for Papyrus

Hi peter,

 

Answers inline below.

 

Thanks,

Quentin

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Peter Cigéhn
Envoyé : jeudi 20 juillet 2017 14:14
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Nightly build repos for Papyrus

 

Hi,

 

I was about the test the fix for bug 516717 and updated my installations of Papyrus for both the Photon and the Oxygen tracks (the bug should be fixed on both tracks). But when checking the contents of the p2 nightly repos 

 

 

they seem to "lag behind" compared to the latest builds on Hudson

 

 

Apart from that they seem to have *identical* versions of plugins, which gives me a feeling that either one of the nightly repos for Photon or Oxygen is a copy of the other (some mis-configuration of the copying maybe?)

 

I have already from before been rather puzzled when trying to test some of the sequence diagram related bugs that were supposed to be fixed on the Photon track, but I could not really see much improvement. If there is a lag, and also incorrect contents in the p2 repos, that might then explain why I really could not see any improvements in the sequence diagram behavior based on the bugs and Gerrit changes that were supposed to be merged.

 

So the questions are:

 

* How often are the nightly repos on download.eclipse.org really updated? If they are lagging behind the latest builds on Hudson, then we have a huge step backwards compared to before when you update your installation directly after the Hudson build was finished.

 

-                      They are updated “nightly” that is every night/day. What was done before was a composite redirecting to the Hudson job hence you downloaded from the Hudson server which is not the cleaner/nicer way to do it as it can overload the build instances for no real reasons. It should also be faster (if I am not mistaken), but the fact that is has not been mirrored yet, as it tends to take more than a day, might have an impact on that end… If you want the latest build you can indeed still fetch it from the Hudson server but that should not be the “go to” address and used only when needed.

 

* Are the correct contents really copied into the Photon or Oxygen nightly repos on download.eclipse.org?

 

-                      I wouldn’t see why they wouldn’t as the latest successful build of the day’s artifacts are copied there by the nightly job. Did you have any problems with it related to this particular thing?

 

* Do I have to revert to pulling the latest build directly from Hudson to really be able to test a fix as soon as the Hudson build is finished in case the copying to download.eclipse.org have some delay, e.g. if it is done only once per day?

 

-                      This was what you did before, albeit transparently, through the composite. As for the sluggishness of the process, I raised a bug on this and am waiting for an answer on this topic. On that note if the answer is that the speed is the “normal” speed provided there then I will revert to the old way or apply suggested improvements if there are any.

 

/Peter Cigéhn

 

PS. Another step backward, at least for me, is that download.eclipse.org is extremely slower than downloading directly from Hudson as it was done before. Earlier I could update my installation for nightly builds of Papyrus in just a few minutes. Now it can take up to 10-20 times longer which has become a real pain. The download speed for download.eclipse.org is around 10-15 kB/s which is really slow compared to what you got from before downloading directly from Hudson. Not sure though if that is only happening to me. DS.

 

-                      As mentioned above this is indeed a problem, not at all only on your end, and is being looked at.


Back to the top