Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "TPTP Build"

(Versioning guideline)
Line 1: Line 1:
TPTP [http://www.eclipse.org/tptp/ main page] > [[TPTP|TPTP Wiki home]] > [[TPTP_Miscellaneous | TPTP Miscellaneous]]
+
TPTP [http://www.eclipse.org/tptp/ main page] > [[TPTP|TPTP Wiki home]] > [[TPTP Miscellaneous|TPTP Miscellaneous]]  
  
== Releng component ==
+
== Releng component ==
  
The TPTP Release Engineering (Releng) component refers to the plug-in org.eclipse.hyades.releng.builder in the TPTP Platform project. It contains all the the build scripts that are used during a TPTP build. The script used to start a TPTP build is in org.eclipse.hyades.releng.builder/master/bash/make.sh. The Java code compiling is handled by the eclipse-build.sh script located in org.eclipse.hyades.releng.builder/master/bash.
+
The TPTP Release Engineering (Releng) component refers to the plug-in org.eclipse.hyades.releng.builder in the TPTP Platform project. It contains all the the build scripts that are used during a TPTP build. The script used to start a TPTP build is in org.eclipse.hyades.releng.builder/master/bash/make.sh. The Java code compiling is handled by the eclipse-build.sh script located in org.eclipse.hyades.releng.builder/master/bash.  
  
Description of the contents of org.eclipse.hyades.releng.builder/master directory:
+
Description of the contents of org.eclipse.hyades.releng.builder/master directory: bash: Contains scripts and utilities used for working with the TPTP builds. java: Contains Java utilities used during the TPTP builds (most utilities are compiled with Java 1.4). ltaconfig: Not currently in use. Contains configuration for the LTA component. maps: Contains the hyades.map file which is used for locating the source during a build. rcpconfig: Not currently in use. Contains configuration for the TPTP RCP builds. runtime: Contains the PDE build file (customTargets.xml) and properties file (build.properties) used during the PDE build, including dependency definitions. templateFiles: Contains the web page template for the driver.  
bash: Contains scripts and utilities used for working with the TPTP builds.
+
java: Contains Java utilities used during the TPTP builds (most utilities are compiled with Java 1.4).
+
ltaconfig: Not currently in use. Contains configuration for the LTA component.
+
maps: Contains the hyades.map file which is used for locating the source during a build.
+
rcpconfig: Not currently in use. Contains configuration for the TPTP RCP builds.
+
runtime: Contains the PDE build file (customTargets.xml) and properties file (build.properties) used during the PDE build, including dependency definitions.
+
templateFiles: Contains the web page template for the driver.
+
  
The org.eclipse.hyades.releng.builder/releases directory contains information specific to each release, such as which features and plug-ins versions have changed.
+
The org.eclipse.hyades.releng.builder/releases directory contains information specific to each release, such as which features and plug-ins versions have changed.  
  
org.eclipse.hyades.releng.builder/updatesite contains the scripts used for creating the TPTP site.xml for the update site.
+
org.eclipse.hyades.releng.builder/updatesite contains the scripts used for creating the TPTP site.xml for the update site.  
  
== BVT/Tools component ==
+
== BVT/Tools component ==
Build Verification Test (BVT) scripts are located in platform/org.eclipse.tptp.platform.releng.tools/org/eclipse/tptp/platform/releng/tools/testautomation. For details on using the BVT, refer to the readme.html.
+
  
The tools which are jars in platform/org.eclipse.hyades.releng.builder/master/java that are used during the build are from platform/org.eclipse.tptp.platform.releng.tools.
+
Build Verification Test (BVT) scripts are located in platform/org.eclipse.tptp.platform.releng.tools/org/eclipse/tptp/platform/releng/tools/testautomation. For details on using the BVT, refer to the readme.html.  
  
== Dependencies ==
+
The tools which are jars in platform/org.eclipse.hyades.releng.builder/master/java that are used during the build are from platform/org.eclipse.tptp.platform.releng.tools.
  
Dependencies are the pre-requisite projects that TPTP build depends on. All these project need to be included inside the eclipse sdk /plugins or /dropins. Currently TPTP includes dependencies from EMF, XSD, WTP, BIRT, DTP, GEF, Equinox OSGI and Eclipse Orbit.
+
== Dependencies ==
  
== Hardware setup ==
+
Dependencies are the pre-requisite projects that TPTP build depends on. All these project need to be included inside the eclipse sdk /plugins or /dropins. Currently TPTP includes dependencies from EMF, XSD, WTP, BIRT, DTP, GEF, Equinox OSGI and Eclipse Orbit.
  
TPTP builds on windows and linux 32bits(ia32), 64bits(em64t) and ipf. For the hardware set up please refers to the table below.
+
== Hardware setup  ==
  
== Map file for source ==
+
TPTP builds on windows and linux 32bits(ia32), 64bits(em64t) and ipf. For the hardware set up please refers to the table below.
  
hyades.map is located inside plugin org.eclipse.hyades.releng.builder/master/maps/ in platform project. It tells which plugins and features at which verison should be checked out before the build.
+
<br>
  
== Versioning guideline ==
+
{| width="200" cellspacing="1" cellpadding="1" border="1"
TPTP version numbering is based on the Eclipse guidelines described in [[Version_Numbering]].
+
|-
 +
| Platform<br>
 +
| OS<br>
 +
| Compiler<br>
 +
| Usage<br>
 +
| JVM<br>
 +
| Xerces-C<br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
|-
 +
| Windows-ia32<br>
 +
| Windows XP Pro 64 bits Version 2003 SP2<br>
 +
| Microsoft Visual Studio 2005<br>
 +
| Windows IA32 native build machine<br>
 +
| java 1.5.0<br>
 +
| xerces-c_2_6_0-windows_nt-msvc_60<br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
|-
 +
| Windows-em64t<br>
 +
| Windows XP Pro 64 bits Version 2003 SP2<br>
 +
| Windows Server 2003 SP1 SDK <br>
 +
| Windows EM64T native build machine<br>
 +
| java 1.5.0<br>
 +
| xerces-c-src_2_6_0<br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
|-
 +
| Linux-ia32<br>
 +
| RHEL 4 (Nahant Update 6) 64 bits<br>
 +
| gcc version 3.4.6 <br>
 +
| Linux IA32 native build machine<br>
 +
| java 1.5.0<br>
 +
| xerces-c-src_2_6_0<br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
|-
 +
| Linux-em64t<br>
 +
| RHEL 4 (Nahant Update 6) 64 bits<br>
 +
| gcc version 3.4.6 <br>
 +
| Linux EM64T native build machine<br>
 +
| java 1.5.0<br>
 +
| xerces-c-src_2_6_0<br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
| <br>
 +
|}
  
The following example describes how TPTP has updated the version numbers in maintenance releases. The example uses the current release as version 4.7.2, and a previous previous most recent major maintenance release as TPTP 4.6.2.
+
<br>
For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.101 in TPTP 4.6.2, then the version will be 1.0.200.
+
For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.100 in TPTP 4.7.0, then the version will be 1.0.102.
+
  
== Build infrastructure ==
+
== Map file for source  ==
  
== Promotion ==
+
hyades.map is located inside plugin org.eclipse.hyades.releng.builder/master/maps/ in platform project. It tells which plugins and features at which verison should be checked out before the build.
  
Promotion means that we will copy the Development Build one level above in the file system so it can be promoted to either milestone or release build where the Development Build still remains intact.
+
== Versioning guideline  ==
  
== Build Name ==
+
TPTP version numbering is based on the Eclipse guidelines described in [[Version Numbering]].
  
TPTP has four build types: Release Builds, Stable Builds, Candidate Builds and Development Builds. For information about different kinds of builds look [http://www.eclipse.org/tptp/home/downloads/build_types.html here]. For Development Builds, the build ID has the format of TPTP-<version>-<timestamps>. During the Milestones and Release Candidates, TPTP builds will be renamed to TPTP-<version>M#-<timestamps> or TPTP-<version>RC#-<timestamps> depending on which Milestones or Release Candidates is. Please refers to this page for information on [[Helios_Simultaneous_Release|Helios/Simultaneous Release Plan]]. On the GA day, TPTP will be renamed to TPTP-<version>.
+
The following example describes how TPTP has updated the version numbers in maintenance releases. The example uses the current release as version 4.7.2, and a previous previous most recent major maintenance release as TPTP 4.6.2. For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.101 in TPTP 4.6.2, then the version will be 1.0.200. For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.100 in TPTP 4.7.0, then the version will be 1.0.102.
 +
 
 +
== Build infrastructure  ==
 +
 
 +
== Promotion  ==
 +
 
 +
Promotion means that we will copy the Development Build one level above in the file system so it can be promoted to either milestone or release build where the Development Build still remains intact.
 +
 
 +
== Build Name  ==
 +
 
 +
TPTP has four build types: Release Builds, Stable Builds, Candidate Builds and Development Builds. For information about different kinds of builds look [http://www.eclipse.org/tptp/home/downloads/build_types.html here]. For Development Builds, the build ID has the format of TPTP-&lt;version&gt;-&lt;timestamps&gt;. During the Milestones and Release Candidates, TPTP builds will be renamed to TPTP-&lt;version&gt;M#-&lt;timestamps&gt; or TPTP-&lt;version&gt;RC#-&lt;timestamps&gt; depending on which Milestones or Release Candidates is. Please refers to this page for information on [[Helios Simultaneous Release|Helios/Simultaneous Release Plan]]. On the GA day, TPTP will be renamed to TPTP-&lt;version&gt;.  
  
 
--[[User:Samwu.ca.ibm.com|Samwu.ca.ibm.com]] 22:44, 11 March 2011 (UTC)
 
--[[User:Samwu.ca.ibm.com|Samwu.ca.ibm.com]] 22:44, 11 March 2011 (UTC)

Revision as of 11:50, 21 March 2011

TPTP main page > TPTP Wiki home > TPTP Miscellaneous

Releng component

The TPTP Release Engineering (Releng) component refers to the plug-in org.eclipse.hyades.releng.builder in the TPTP Platform project. It contains all the the build scripts that are used during a TPTP build. The script used to start a TPTP build is in org.eclipse.hyades.releng.builder/master/bash/make.sh. The Java code compiling is handled by the eclipse-build.sh script located in org.eclipse.hyades.releng.builder/master/bash.

Description of the contents of org.eclipse.hyades.releng.builder/master directory: bash: Contains scripts and utilities used for working with the TPTP builds. java: Contains Java utilities used during the TPTP builds (most utilities are compiled with Java 1.4). ltaconfig: Not currently in use. Contains configuration for the LTA component. maps: Contains the hyades.map file which is used for locating the source during a build. rcpconfig: Not currently in use. Contains configuration for the TPTP RCP builds. runtime: Contains the PDE build file (customTargets.xml) and properties file (build.properties) used during the PDE build, including dependency definitions. templateFiles: Contains the web page template for the driver.

The org.eclipse.hyades.releng.builder/releases directory contains information specific to each release, such as which features and plug-ins versions have changed.

org.eclipse.hyades.releng.builder/updatesite contains the scripts used for creating the TPTP site.xml for the update site.

BVT/Tools component

Build Verification Test (BVT) scripts are located in platform/org.eclipse.tptp.platform.releng.tools/org/eclipse/tptp/platform/releng/tools/testautomation. For details on using the BVT, refer to the readme.html.

The tools which are jars in platform/org.eclipse.hyades.releng.builder/master/java that are used during the build are from platform/org.eclipse.tptp.platform.releng.tools.

Dependencies

Dependencies are the pre-requisite projects that TPTP build depends on. All these project need to be included inside the eclipse sdk /plugins or /dropins. Currently TPTP includes dependencies from EMF, XSD, WTP, BIRT, DTP, GEF, Equinox OSGI and Eclipse Orbit.

Hardware setup

TPTP builds on windows and linux 32bits(ia32), 64bits(em64t) and ipf. For the hardware set up please refers to the table below.


Platform
OS
Compiler
Usage
JVM
Xerces-C




Windows-ia32
Windows XP Pro 64 bits Version 2003 SP2
Microsoft Visual Studio 2005
Windows IA32 native build machine
java 1.5.0
xerces-c_2_6_0-windows_nt-msvc_60




Windows-em64t
Windows XP Pro 64 bits Version 2003 SP2
Windows Server 2003 SP1 SDK
Windows EM64T native build machine
java 1.5.0
xerces-c-src_2_6_0




Linux-ia32
RHEL 4 (Nahant Update 6) 64 bits
gcc version 3.4.6
Linux IA32 native build machine
java 1.5.0
xerces-c-src_2_6_0




Linux-em64t
RHEL 4 (Nahant Update 6) 64 bits
gcc version 3.4.6
Linux EM64T native build machine
java 1.5.0
xerces-c-src_2_6_0





Map file for source

hyades.map is located inside plugin org.eclipse.hyades.releng.builder/master/maps/ in platform project. It tells which plugins and features at which verison should be checked out before the build.

Versioning guideline

TPTP version numbering is based on the Eclipse guidelines described in Version Numbering.

The following example describes how TPTP has updated the version numbers in maintenance releases. The example uses the current release as version 4.7.2, and a previous previous most recent major maintenance release as TPTP 4.6.2. For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.101 in TPTP 4.6.2, then the version will be 1.0.200. For a feature or plug-in that was version 1.0.101 in TPTP 4.7.1. If the content changes in the current release (TPTP 4.7.2) and the version was 1.0.100 in TPTP 4.7.0, then the version will be 1.0.102.

Build infrastructure

Promotion

Promotion means that we will copy the Development Build one level above in the file system so it can be promoted to either milestone or release build where the Development Build still remains intact.

Build Name

TPTP has four build types: Release Builds, Stable Builds, Candidate Builds and Development Builds. For information about different kinds of builds look here. For Development Builds, the build ID has the format of TPTP-<version>-<timestamps>. During the Milestones and Release Candidates, TPTP builds will be renamed to TPTP-<version>M#-<timestamps> or TPTP-<version>RC#-<timestamps> depending on which Milestones or Release Candidates is. Please refers to this page for information on Helios/Simultaneous Release Plan. On the GA day, TPTP will be renamed to TPTP-<version>.

--Samwu.ca.ibm.com 22:44, 11 March 2011 (UTC)

Back to the top