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.
Difference between revisions of "Papyrus/Papyrus Developer Guide/Build Process"
(First draft of the page) |
|||
| Line 1: | Line 1: | ||
| − | = Description of the build<br> = | + | = Description of the build<br> = |
| − | Papyrus MDT project is currently build using the [[ | + | Papyrus MDT project is currently build using the [[Athena Common Build|Athena Common Build]]. [https://build.eclipse.org/hudson/job/cbi-papyrus-0.7-nightly/] |
| − | [https://build.eclipse.org/hudson/job/cbi-papyrus-0.7-nightly/ One hudson job] builds Papyrus from the SVN repository using the trunk version of the code. It produces the nightly build (N) of the tool.<br> | + | [https://build.eclipse.org/hudson/job/cbi-papyrus-0.7-nightly/ One hudson job] builds Papyrus from the SVN repository using the trunk version of the code. It produces the nightly build (N) of the tool.<br> |
| − | A second one should be installed when the Papyrus code will be more stable, building integration (I) builds. | + | 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 = | + | = How to add a plugin and or a set of plugins in the build process of Papyrus = |
| − | The hudson job gathers sources from the Eclipse SVN repository. It does have 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 sources from the Eclipse SVN repository. It does have 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> |
| + | == Adding a plugin == | ||
| + | To add a plugin in the build process, it has to be added to the [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/org.eclipse.papyrus.releng/maps/ 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. <br> | ||
| + | The second step is to add it to an existing feature or create a new feature that will be added to the build process. See Adding a feature below. | ||
| + | == Adding a feature<br> == | ||
| − | + | <br> | |
| − | I would like to thank Nick Boldt and the [[MoDisco|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/ | + | = Special Thanks = |
| + | |||
| + | I would like to thank Nick Boldt and the [[MoDisco|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/How it Works|Modisco Releng]] part in the Eclipse Wiki | ||
Revision as of 06:37, 18 December 2009
Contents
Description of the build
Papyrus MDT project is currently build using the Athena Common Build. [1]
One 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 sources from the Eclipse SVN repository. It does have 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.
Adding a plugin
To add a plugin in the build process, it has to 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 to an existing feature or create a new feature that will be added to the build process. See Adding a feature below.
Adding a feature
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