Difference between revisions of "Modeling Project Releng/Building/Signing And Packing"

From Eclipsepedia

Jump to: navigation, search
m (Process: note about missing MANIFEST.MF files in source plugins)
m (Process: note about bug 173651)
Line 52: Line 52:
  
 
5. Use the Master zip as input to the [http://dev.eclipse.org/viewcvs/index.cgi/releng-common/tools/scripts/buildUpdate.sh?root=Modeling_Project&view=markup buildUpdate.sh] script, by updating your [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.m2t/org.eclipse.jet.releng/promoteToEclipse.jet.properties?root=Modeling_Project&view=markup promoteToEclipse.*.properties] [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.gef/org.eclipse.gef.releng/promoteToEclipse.gef.properties?root=Tools_Project&view=markup file].
 
5. Use the Master zip as input to the [http://dev.eclipse.org/viewcvs/index.cgi/releng-common/tools/scripts/buildUpdate.sh?root=Modeling_Project&view=markup buildUpdate.sh] script, by updating your [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.m2t/org.eclipse.jet.releng/promoteToEclipse.jet.properties?root=Modeling_Project&view=markup promoteToEclipse.*.properties] [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.gef/org.eclipse.gef.releng/promoteToEclipse.gef.properties?root=Tools_Project&view=markup file].
 +
:*<b style="color:red">NOTE!</b> This is currently NOT recommended due to a bug with source plugin manifest.mf corruption. See {{bug|173651}}
  
 
{{codeblock|<nowiki># zip to use for UM jar generation
 
{{codeblock|<nowiki># zip to use for UM jar generation

Revision as of 16:22, 22 February 2008

This document is a work in progress.

Contents

Requirements

1. You must have permission to ssh to build.eclipse.org. This is where the signing will occur.

2. You must be able to ssh from your build server to build.eclipse.org without being prompted for a host key or password. The first time you try to connect from your build server, accept the host key and you should never be prompted again. If you can ssh from your build server to dev.eclipse.org or download1.eclipse.org, you should be able to connect to build.eclipse.org using the same credentials and ssh key.

3. While on build.eclipse.org, you must be able to create files in your staging folder, eg., /home/data/httpd/download-staging.priv/modeling/emft.

4. While on build.eclipse.org, you must be able to run /usr/bin/jarsigner.

If you cannot do any of the above things, open a bug and ask for access. cc: your PMC for approval and optionally, User:Nickb.

Process

1. Create an "all" or "master" feature, which will build SDK, examples, and any other features you might build. This obsoletes the need for an SDK builder, runtime builder, doc builder, and examples builder. You can still use your custom doc plugin builder; this just cleans up some redundancies in your .releng project.

If your SDK feature already contains all your smaller features (including runtime, source, doc, and examples, but not tests) then you don't need a new "all" feature.

2. Add this new feature to your map file.

3. Add a new builder/all/ folder in your .releng project. Your old builder/sdk, builder/doc, builder/examples folders are no longer required and can be deleted. As in step 1, if you're reusing your SDK feature, this step is not required. Just update your customTargets.xml to create the Master Zip.

4. Change your .releng/buildAll.xml to use new signing/packing code. You'll notice that many targets have been removed to buildAllHelper.xml to simplify this file, and some things have been reordered. The most important change is that you must now define your own packaging; however, by only doing a single PDE build for the whole "All" feature (and a second one for your tests), your build will run faster. This is important because jar signing can take a few minutes or as much as an hour, depending on the queue ahead of your build.

NOTE! Make sure that all your files are properly appearing the the newly-constructed zips. As discovered in bug 173651 comment 10, you need to be sure that your source plugins' MANIFEST.MF files are properly included.

<include name="**/org.eclipse.gef*" />
<include name="**/org.eclipse.gef*/**" />
<include name="**/org.eclipse.gef*/**/**" />

Should you want to disable signing, comment out the "sign" variable declaration:

<!-- <property name="sign" value="true" /> DISABLED FOR NOW -->

5. Use the Master zip as input to the buildUpdate.sh script, by updating your promoteToEclipse.*.properties file.

  • NOTE! This is currently NOT recommended due to a bug with source plugin manifest.mf corruption. See bug 173651
# zip to use for UM jar generation
filePrefixesToUnzipArray=( "$projectName-$subprojectName-Master-" );

6. Add pack200="true" to all your update site's site*.xml files:

<site pack200="true" ...>

7. Promote as before.

Testing / Install Verification

When you install your signed features from the update site, you should see something like this:

Gef-3.4-signed-features.png

Bugs

  • bug 173651: Support Pack200 in Modeling builds / update sites
  • bug 217929: M2T Signing & Packing
  • bug 217945: Problems with file permissions in signed/packed jars
  • bug 211613: JDK 6's Pack200 is not backward compatible with JDK 5 if packed jars contain no classfiles

References