Skip to main content
Jump to: navigation, search

Modeling Project Releng/Migrate to a new server

< Modeling Project Releng
Revision as of 13:00, 7 July 2009 by (Talk | contribs) (Option 1: Migrate to using existing Modeling Build)

Next week, Wednesday July 15 at 9:00am ET, will be going off the air (bug 273485.

As such, you will need to move your build infrastructure to, or you might want to explore running your build using the new Athena Build system on

Option 1: Migrate to using existing Modeling Build

To move to modeling.eclipse, here's a checklist of things to do / test.

Verify that pages on emft.eclipse exist on modeling.eclipse

For example...

If any builds are missing, you can use scp or rsync to move them from emft.eclipse or download.eclipse -> modeling.eclipse yourself).

Verify that you can build successfully on the new server

Run a build. Verify that everything works - from signing & packing to ssh access


=== Publish a build. Verify that ssh permissions are correct and that the update site is properly generated.


Option 2: Migrate to using new Athena Build

This will take more work, but the benefit here is you can run your build locally in Eclipse or on using Hudson to manage it (instead of the custom web UI on emft.eclipse or modeling.eclipse). Also, the amount of configuration is significantly less, so ongoing maintenance is less. (The Modeling Build is also deprecated in favour of the Athena Build.)

You will need a new .releng project in CVS. Name/path does not matter.

Here are some examples to copy from - see ve, vtp, gef, linux tools, nebula widgets.


Once that's set up and you can build locally in Eclipse, see:

Back to the top