View source for Modeling Project Releng/Migrate to a new server

Next week, Wednesday July 15 at 9:00am ET, emft.eclipse.org will be going off the air ({{bug|273485}}. 

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

== Option 1: Migrate to modeling.eclipse.org 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...

 http://emft.eclipse.org/modeling/gmf/downloads/
  vs
 http://modeling.eclipse.org/modeling/gmf/downloads/

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 ===

 http://emft.eclipse.org/modeling/gmf/gmf/build/
  vs
 http://modeling.eclipse.org/modeling/gmf/gmf/build/

First, edit your /www/modeling/<project>/<subproject>/build/_common.php file to add a new entry for the new server. Commit your changes to CVS.

Next, check out the changed file:

 cd /var/www/html/modeling/<project>/<subproject>/build/; cvs up

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

See: http://wiki.eclipse.org/Modeling_Project_Releng/Building

=== Verify that you can test successfully on the new server ===

You may find your tests fail to run due to a hardcoded platform arch value in your [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.gef/org.eclipse.gef.releng/builder/tests/configs/local/relengbuildgtk.sh?root=Tools_Project&content-type=text%2Fplain&view=co relengbuildgtk.sh] script. You can fix this by replacing "<code>basearch=x86</code>" with "<code>basearch=x86_64</code>".

See also https://bugs.eclipse.org/bugs/attachment.cgi?id=135389 and {{bug|253114}}.

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

See: http://wiki.eclipse.org/Modeling_Project_Releng/Releasing#The_First_Time

== Option 2: Migrate to build.eclipse.org using new Athena Build ==

This will take more work, but the benefit here is you can run your build locally in Eclipse or on build.eclipse.org 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.)

=== Create a new .releng project ===

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

Here are [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/?root=Technology_Project some examples] to copy from - see ve, vtp, gef, linux tools, nebula widgets.

See: http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Eclipse

=== Run build in Eclipse ===

Once that's set up, you can run the build.xml script using Run As > Ant Build to get build and test results locally in Eclipse. Note that tests only work on Linux. See http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Eclipse#Troubleshooting_.2F_server_setup


=== Run build in Hudson on build.eclipse.org ===

Next, see: http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson


[[Category:Modeling]]
[[Category:Releng]]