Difference between revisions of "Imeji release process"
Jump to navigation
Jump to search
(Created page with "This page describes how to release imeji. =Release sub-modules= The first step is to release the submodules using imeji: * The common presentation * The fledgeddata service The ...") |
|||
| Line 6: | Line 6: | ||
* The fledgeddata service | * The fledgeddata service | ||
The release process is the same for both: | The release process is the same for both: | ||
*Checkout the code in a new directory | |||
* Prepare the release | |||
<pre>mvn release:prepare -DpreparationGoals="clean install" -DupdateReleaseInfo=true</pre> | |||
* if the build was successfull | |||
<pre>mvn release:perform</pre> | |||
* In case of error: | |||
<pre>mvn release:rollback</pre> | |||
=Release imeji= | =Release imeji= | ||
To release imeji, Git is necessary. For Windows, we use the Windows PowerShell (available via Github client). The steps are: | To release imeji, Git is necessary. For Windows, we use the Windows PowerShell (available via Github client). The steps are: | ||
* Switch to the release branch. This branch should have been created by the repository manager. | |||
<pre> | |||
git checkout release_branch | |||
git pull | |||
</pre> | |||
* Change the sub-modules dependencies with the release version created during their release and commit: | |||
<pre> | |||
git add pom.xml | |||
git add ./imeji_ear/pom.xml | |||
git add ./imeji_presentation/pom.xml | |||
git commit -m 'Submodules version changed to last release number' | |||
git push | |||
</pre> | |||
[[Category:Imeji_Technical_Specification|Imeji.org]] | [[Category:Imeji_Technical_Specification|Imeji.org]] | ||
Revision as of 12:07, 9 October 2012
This page describes how to release imeji.
Release sub-modules[edit]
The first step is to release the submodules using imeji:
- The common presentation
- The fledgeddata service
The release process is the same for both:
- Checkout the code in a new directory
- Prepare the release
mvn release:prepare -DpreparationGoals="clean install" -DupdateReleaseInfo=true
- if the build was successfull
mvn release:perform
- In case of error:
mvn release:rollback
Release imeji[edit]
To release imeji, Git is necessary. For Windows, we use the Windows PowerShell (available via Github client). The steps are:
- Switch to the release branch. This branch should have been created by the repository manager.
git checkout release_branch git pull
- Change the sub-modules dependencies with the release version created during their release and commit:
git add pom.xml
git add ./imeji_ear/pom.xml
git add ./imeji_presentation/pom.xml
git commit -m 'Submodules version changed to last release number'
git push