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 "PackageDrone/ReleaseBuild"
m |
|||
| Line 20: | Line 20: | ||
mvn clean install | mvn clean install | ||
cd .. | cd .. | ||
| − | mvn clean verify -Prpm - | + | mvn clean verify -Prpm -Pjdeb-sign -Dtycho.localArtifacts=ignore |
== Assembling outputs == | == Assembling outputs == | ||
… | … | ||
Revision as of 08:19, 18 January 2016
This page tries to describe the internal build process for releases.
Prerequisites
- Maven 3.3.x with
mvnin the "PATH" -
gpg-agentand a working signing key - rpm build tools installed
Have the following properties set in your ~/.m2/settings.xml or provide these during the builds:
<jdeb.keyring>/path/to/gpg/keyring</jdeb.keyring> <jdeb.key>12345678</jdeb.key> <jdeb.passphrase>passphrase</jdeb.passphrase>
Performing the build
git clone https://github.com/eclipse/packagedrone.git packagedrone.git cd packagedrone.git cd runtime mvn clean install cd .. mvn clean verify -Prpm -Pjdeb-sign -Dtycho.localArtifacts=ignore
Assembling outputs
…