Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseSCADA/Development/Build"
(Created page with "Building Eclipse SCADA == Pre-Requisites == * Maven 3.0+ * Java 1.7 (JDK) * Git == Repositories == === org.eclipse.scada.external.git === git clone git://git.eclipse.org...") |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == About == | |
| + | |||
| + | This document describes Eclipse SCADA version 0.1.0. For newer versions you might need to replace the version in some commands. | ||
| + | |||
| + | For a description of the different repositories see [[EclipseSCADA/Plan/RepositoryLayout]]. | ||
== Pre-Requisites == | == Pre-Requisites == | ||
| Line 7: | Line 11: | ||
* Git | * Git | ||
| − | == | + | == Full Build == |
| − | + | First it is best to create an empty build directory for starting: | |
| + | |||
| + | mkdir build | ||
| + | cd build | ||
| + | |||
| + | In order to perform a full build you will need to check out all repositories first: | ||
git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.external.git | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.external.git | ||
| − | + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.utils.git | |
| − | mvn | + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.chart.git |
| − | + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.protocols.git | |
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.base.git | ||
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.core.git | ||
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.hmi.git | ||
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.ide.git | ||
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.deploy.git | ||
| + | git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.releng.git | ||
| + | |||
| + | Now trigger the aggregated build script: | ||
| + | |||
| + | cd org.eclipse.scada.releng/aggregator | ||
| + | mvn clean verify | ||
| + | |||
| + | If you want .rpm files to be build you will need to install "rpmbuild" locally and add the "rpm" profile | ||
| + | mvn -Prpm clean verify | ||
| + | |||
| + | If you want .deb files to be build you will need to add the "deb" profile: | ||
| + | mvn -Pdeb clean verify | ||
| + | |||
| + | It is possible to combine multiple profiles, like: | ||
| + | |||
| + | mvn -Pdeb -Prpm clean verify | ||
| + | |||
| + | == Maven/Tycho Profiles == | ||
| + | |||
| + | The following profiles work on all repositories: | ||
| + | |||
| + | ;deb | ||
| + | : create debian package file from P2 repository | ||
| + | ;rpm | ||
| + | : create redhat package file from P2 repository. You need the "rpmbuild" command on your local system in addition. | ||
| + | ;eclipse-sign | ||
| + | : sign resulting P2 jars (only works on eclipse build system) | ||
| + | ;eclipse-hudson | ||
| + | : copy build artifacts to local directory "../output" and eclipse download location (only works on eclipse build system) | ||
| + | |||
| + | == Eclipse Hudson instance == | ||
| + | |||
| + | https://hudson.eclipse.org/scada/ | ||
| + | |||
| + | == Cleanup to archive.eclipse.org == | ||
| + | |||
| + | The job https://hudson.eclipse.org/eclipsescada/job/archive performs the transfer of older builds to <code>archive.eclipse.org</code>. | ||
| + | |||
| + | The job has to be configured to work on specific builds. | ||
Latest revision as of 07:57, 6 June 2016
Contents
About
This document describes Eclipse SCADA version 0.1.0. For newer versions you might need to replace the version in some commands.
For a description of the different repositories see EclipseSCADA/Plan/RepositoryLayout.
Pre-Requisites
- Maven 3.0+
- Java 1.7 (JDK)
- Git
Full Build
First it is best to create an empty build directory for starting:
mkdir build cd build
In order to perform a full build you will need to check out all repositories first:
git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.external.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.utils.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.chart.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.protocols.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.base.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.core.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.hmi.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.ide.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.deploy.git git clone git://git.eclipse.org/gitroot/eclipsescada/org.eclipse.scada.releng.git
Now trigger the aggregated build script:
cd org.eclipse.scada.releng/aggregator mvn clean verify
If you want .rpm files to be build you will need to install "rpmbuild" locally and add the "rpm" profile
mvn -Prpm clean verify
If you want .deb files to be build you will need to add the "deb" profile:
mvn -Pdeb clean verify
It is possible to combine multiple profiles, like:
mvn -Pdeb -Prpm clean verify
Maven/Tycho Profiles
The following profiles work on all repositories:
- deb
- create debian package file from P2 repository
- rpm
- create redhat package file from P2 repository. You need the "rpmbuild" command on your local system in addition.
- eclipse-sign
- sign resulting P2 jars (only works on eclipse build system)
- eclipse-hudson
- copy build artifacts to local directory "../output" and eclipse download location (only works on eclipse build system)
Eclipse Hudson instance
https://hudson.eclipse.org/scada/
Cleanup to archive.eclipse.org
The job https://hudson.eclipse.org/eclipsescada/job/archive performs the transfer of older builds to archive.eclipse.org.
The job has to be configured to work on specific builds.