Jump to: navigation, search

Difference between revisions of "Modeling Project Releng/Branching"

(New page: == Branching == To support both a HEAD and an Rx_y_maintenance branch, you need to branch your cvs repository. This is accomplished easily using Eclipse or commandline CVS. In Eclipse, s...)
 
m (Branching)
Line 19: Line 19:
 
The [[Platform-releng-basebuilder|recommended list of tags for use with org.eclipse.releng.basebuilder is located here]] and updated when new tags are added (usually once a miletone).
 
The [[Platform-releng-basebuilder|recommended list of tags for use with org.eclipse.releng.basebuilder is located here]] and updated when new tags are added (usually once a miletone).
  
 +
===Troubleshooting FAQ ===
  
 +
====I chose to build my maintenance branch from the web ui, but the built plugins are coming from HEAD. ====
  
{| border="1" cellpadding="2"
+
Check that your map file of your maintenance branch releng plugin refers to the branched plugin and not to HEAD.
| '''Problem'''
+
| '''Solution'''
+
|- valign="top"
+
| I chose to build my maintenance branch from the web ui, but the built plugins are coming from HEAD.
+
| Check that your map file of your maintenance branch releng plugin refers to the branched plugin and not to HEAD.
+
|}
+
  
  
 
[[Category:Modeling]] [[Category:Releng]]
 
[[Category:Modeling]] [[Category:Releng]]

Revision as of 16:53, 1 October 2007

Branching

To support both a HEAD and an Rx_y_maintenance branch, you need to branch your cvs repository. This is accomplished easily using Eclipse or commandline CVS.

In Eclipse, select your plugins, then right-click and do Team > Branch...

If you're following the usual convention, you'd do your Eclipse 3.3 compatible work in HEAD and your Eclipse 3.2 work in a maintenance branch. Taking the JET Editor project as an example, you'd do something like this:

  1. build a 0.7.0 R build. Use type "R" (Release), then set the build alias field on the build page to "0.7.0".
  2. create a branch called R0_7_maintenance, with root R0_7_0. (You'll create a redundant, but potentially handy tag for your 0.7.0 release.)
  3. begin doing "R0_7_maintenance | 0.7.1" builds from your build page at /emft/build/?project=jeteditor. Pick Eclipse 3.2 driver from the list (they'll have M or R).
  4. at the same time, start on your Eclipse 3.3 development, then kick builds using "HEAD | 0.8.0" from the picker on the build page. Select an Eclipse 3.3 driver (they have I or S or R). You can get these from here: http://download.eclipse.org/eclipse/downloads/

NOTE: be sure to copy just the http path to the tar.gz file, without ?file= querystring stuff in it. For example:

The recommended list of tags for use with org.eclipse.releng.basebuilder is located here and updated when new tags are added (usually once a miletone).

Troubleshooting FAQ

I chose to build my maintenance branch from the web ui, but the built plugins are coming from HEAD.

Check that your map file of your maintenance branch releng plugin refers to the branched plugin and not to HEAD.