Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Ganymede End of Days: RC5 week

Yes, on emft.eclipse the build user is "apache" and on emf.torolab it's "www-data". Both use /home/www-data as their home dir.

This has been fixed and rolled out on and emf.torolab -- the temp folder is now located in /tmp/ instead of the user's (incorrect) home dir. Thanks for the bug report!

If you've already done all the string renames in build.cfg and the text/links look good on your build page on, eg:

then yes, all you need to do is update build.cfg to point to the correct platform driver and promote the build on Tuesday. You can optionally run a new N or I build w/ the latest platform bits, if you want to be sure they didn't break anything, but there's no need to promote such a test-build.

Thanks for being ahead of the curve!

It requires the user -u apache in order to get permissions for builds manipulation (script usage sample tells us to use -u www-data, but there are no such user, so I guessed it should be the default build user), but the temp directory name is set to :

that does not work because /home/apache/... can't be created. So I have created the copy of script (/home/www-data/build/modeling/scripts/ with the only change:

and used the modified script for renaming. After changing the buildType=S into buildType=R in the build.cfg, I believe that the only change required for U2T is replacement of the platform release build URL.

Regards, Michael

-----Original Message-----
From: on behalf of Christian W. Damus
Sent: Wed 6/18/2008 1:24 PM
To: MDT developers
Subject: Re: [] Ganymede End of Days: RC5 week
Hi, Michael,

For my components, I have been waiting for the word "go" from Nick. I think that isn't expected until the "Final Daze" next week.

The usual procedure in these coordinated releases has been, during the final days, for the projects to share the URLs to their future release bits on the cross-project/planning-council mailing list. Eclipse Platform and EMF are always fairly prompt in sharing these URLs.

As far as the OCL and EMF Query/Transaction/Validation components are concerned, though, you can bet that they will look like last year's ZIP names (1.2.0 instead of 1.1.0) with build-folder names identical to the last S-build, but with 'R' instead of 'S'.



On 18-Jun-08, at 7:05 AM, Michael Golubev wrote:

Hello, all

Has anyone already processed the renaming?

As far as I see, there are no R builds for my dependencies in the emft build server, say, in the EMF query download folder ( ) I actually see only S builds.

The problem I am facing is the replacement string for platform release build id, that is, in the usage examples, the string pairs like these two:

eclipse-SDK-M20060609-1217-linux-gtk.tar.gz=eclipse-SDK-3.2-linux- gtk.tar.gz \
M20060609-1217=R-3.2-200606281325 \
The first one can be easily guessed for upcoming release, in our case it will be:

eclipse-SDK-3.4RC4-linux-gtk.tar.gz=eclipse-SDK-3.4-linux-gtk.tar.gz \

(Is it correct?)

but I can't understand what is the proper replacement for the second one.
There are no platform release builds at the download page,
and its not clear for me where to find the build ID for replacement.

I can only guess that the usage sample is a bit outdated, and there are no references to exact build ID in our actual staff anymore. Is it correct?

Right now, I am going to just try renaming with problem replacement pair omitted, and check that there are no references to the problem one.

-----Original Message-----
From: on behalf of Christian W. Damus
Sent: Fri 6/13/2008 11:09 PM
To: MDT developers
Subject: Re: [] Ganymede End of Days: RC5 week

Hi, Nick,

OCL RC4 is golden for me. Likewise Query, Transaction, and Validation.

Good thing, too, because GMF RC5 is already out! Wouldn't want them to
do an M5a  :-)


On Fri, 2008-06-13 at 14:59 -0400, Nick Boldt wrote:


-------- Original Message --------

I'd like a show of hands from the various projects -- who need an RC5
build next week, and who are fine with renaming their RC4 or RC4a builds?

The reason I ask is because next week is the LAST chance to get anything
changed, and we need everything in place by EOD Wednesday so that the
final EPP packages can be built.

***At this time, I'm going to assume that NO ONE will need an RC5 build, so disillusion me ASAP if that's not the case. Everyone downstream from
you will need to be building with this updated build.***

Once the platform has declared what its final build will be called (and posted it on the Signoffs page [1], everyone can run the
[2] script to copy their RC4(a)/RC5 build's bits and fix up any
references to previously-named builds.


For those high up the stack (EMF, GEF, Net4j) this means that you'll run
this script and fix up any references to the Eclipse driver used. For
those lower down, you need to replace a lot more strings (EMF, UML2,
OCL, GMF, etc.). If you don't like the automated old=new pair syntax,
you can do this by hand. Just edit your R build's build.cfg file to fix
up the references so that your build page will correctly list the R
builds, not the RC builds. You *do* still have to run the script to
rename all the zips and the md5 files, but the script manipulation can
be done the hard way if you prefer. :)

Once everyone has their builds renamed, ***DO NOT PUBLISH*** them until
we get the green light to do so on Monday June 24 [3].


Any questions, please don't hesitate. Let's have a smooth final RC week
and an even smoother Release day!

Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV

<winmail.dat>_______________________________________________ mailing list

Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV
E-mail: cdamus@xxxxxxxxxxxxx
Tel: 819.684.9639 x229

_______________________________________________ mailing list


_______________________________________________ mailing list

Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling ::

Back to the top