Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/Papyrus Developer Guide/Build Process"

m
m
Line 11: Line 11:
 
The hudson job gathers itself sources from the Eclipse SVN repository. Doing so, the build workspace contains a set of folders, but does not know which folder contains the plugins, the features, etc. This is the role of the map file, placed in the [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/org.eclipse.papyrus.releng/ Papyrus releng project], in the maps sub-folder. This map file describes the set of plugins placed in the SVN repository, and which version should be used. In the night build process, we are using trunk version of the plugins/features.<br>  
 
The hudson job gathers itself sources from the Eclipse SVN repository. Doing so, the build workspace contains a set of folders, but does not know which folder contains the plugins, the features, etc. This is the role of the map file, placed in the [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/org.eclipse.papyrus.releng/ Papyrus releng project], in the maps sub-folder. This map file describes the set of plugins placed in the SVN repository, and which version should be used. In the night build process, we are using trunk version of the plugins/features.<br>  
  
First of all, you have to <u>create a bug</u> in the papyrus bugzilla, under the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=263430 Add Releng] task. So we can have a trace of which plugin has been added, by who and when. See the following [https://bugs.eclipse.org/bugs/show_bug.cgi?id=296736 bug] for example  
+
First of all, you have to [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=MDT add a bug]in the papyrus bugzilla, under the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=263430 Add Releng] task. So we can have a trace of which plugin has been added, by who and when. See the following [https://bugs.eclipse.org/bugs/show_bug.cgi?id=296736 bug] for example  
  
 
== Adding a plugin<br>  ==
 
== Adding a plugin<br>  ==

Revision as of 06:50, 20 May 2010

Description of the build

Papyrus MDT project is currently build using the Athena Common Build.

This hudson job builds Papyrus from the SVN repository using the trunk version of the code. It produces the nightly build (N) of the tool.

A second one should be installed when the Papyrus code will be more stable, building integration (I) builds.

How to add a plugin and or a set of plugins in the build process of Papyrus

The hudson job gathers itself sources from the Eclipse SVN repository. Doing so, the build workspace contains a set of folders, but does not know which folder contains the plugins, the features, etc. This is the role of the map file, placed in the Papyrus releng project, in the maps sub-folder. This map file describes the set of plugins placed in the SVN repository, and which version should be used. In the night build process, we are using trunk version of the plugins/features.

First of all, you have to add a bugin the papyrus bugzilla, under the Add Releng task. So we can have a trace of which plugin has been added, by who and when. See the following bug for example

Adding a plugin

  • To add a plugin in the build process, it must be added to the map file of the releng project. The entries in this file are ordered as they are placed on the SVN repository. For maintenance purpose, the new plugin should be placed using this order. As building the papyrus tool, the build process will checkout files using the information of the map file.
  • The second step is to add it as a packaged plugin to an existing feature or create a new feature that will be added to the build process (See Adding a feature below).
  • Commit your modifications to the SVN repository (map file in the releng project, feature referencing this packaged plugin, and your plugin itself)
  • You can then manually lauch the build to test the new configuration using the "Launch a build" button on the left side of the window. If you do not see the button, you are not connected as a papyrus commiter.

Adding a feature

  • To add a feature in the build process, it also has to be added to the map file of the releng project. Do not forget to add also the plugins packaged in this feature, following previous chapter.
  • You must then reference this feature in the main papyrus feature or the feature requiring your new feature.
  • Commit your modifications to the SVN repository (map file in the releng project, feature referencing this new feature, and your feature itself)
  • Finally, manually launch a build to test the configuration.


If the build works, do not forget to close the bugzilla task created in the first point.

Special Thanks

I would like to thank Nick Boldt and the Modisco team for their  help during the initialization of the build process. You can find details about the Athena Build Process in the Modisco Releng part in the Eclipse Wiki

Back to the top