NEW - Bug 365919: [Architecture - SVN - Build] Rewrite the Build

https://bugs.eclipse.org/bugs/show_bug.cgi?id=365919

documentation

6 files changed, 222 insertions, 26 deletions

diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/buildChaining.png b/sandbox/org.eclipse.papyrus.build.documentation/resources/buildChaining.png
new file mode 100644
index 00000000000..c32f68c71ef
--- /dev/null
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/buildChaining.png
diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/docu.mediawiki b/sandbox/org.eclipse.papyrus.build.documentation/resources/docu.mediawiki
index 631a266e6d3..5f20c3a501a 100644
--- a/sandbox/org.eclipse.papyrus.build.documentation/resources/docu.mediawiki
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/docu.mediawiki
@@ -6,17 +6,50 @@
 * have rights to launch this job : https://hudson.eclipse.org/hudson/job/juno.runAggregator/ (should come with the previous rights)

 * have write access to /home/data/httpd/download.eclipse.org/modeling/mdt/papyrus (should come with the Papyrus committer rights)

 

+=== configure password-less ssh access ===

+To run scripts that access the build.eclipse.org server without having to type the ssh password for each operation, you can use ssh-keygen to create a key and put your '''public''' key "~/.ssh/id_rsa.pub" in "~/.ssh/authorized_keys" ([http://linuxproblem.org/art_9.html see this documentation]).

+

 

 == Releng Project ==

 The papyrus releng project is called : '''org.eclipse.mdt.papyrus.releng.buckminster'''

 

 [[Image:releng.png]]

 

-*'''serverConfig :''' (after each modification, the scripts in this directory must be copied into "/shared/modeling/mdt/papyrus" where they run) 

+It contains sub-folders corresponding to each build:

+* papyrus-trunk-nightly

+* papyrus-trunk-nightly-tests

+* papyrus-trunk-nightly-3.8-tests

+* papyrus-trunk-extra-nightly

+* papyrus-trunk-extra-nightly-tests

+

+And each folder contains the configuration for that build:

+*'''build.xml:''' the main ant build script : installs Buckminster, imports the dependencies and the Papyrus projects from SVN, builds the workspace, creates the update site and runs the tests

+*'''build-before.sh:''' does a bit of cleanup and initializes variables for the build

+*'''build-after.sh:''' packages the result in a zip, and triggers the publishing of this zip

+*'''buckminster.cspec :''' describes the top-level dependencies of the build

+*'''build.cquery :''' describes the root request for the Buckminster import, properties for the import (for example, it indicates that the Papyrus source plug-ins should not be materialized during the import, as they are generated by Buckminster during the build), and references the Buckminster rmap

+*'''build.mspec :''' description for the Buckminster '''materialization''' (i.e. import) of artifacts (plug-ins and features), when building on *.eclipse.org

+*'''local.mspec :''' description for the Buckminster materialization when building locally

+*'''build.rmap :''' should be updated for each release. An [https://dev.eclipse.org/svnroot/modeling/org.eclipse.emft.facet/trunk/releng/org.eclipse.emf.facet.releng.tools EMF-Facet plug-in] allows to update it easily using the b3 file. The '''<!-- updateFrom -->''' tags are used by this script. 

+*'''build.properties :''' properties for the build (when building on *.eclipse.org)

+*'''local.properties :''' properties for the build (when building locally)

+

+And these scripts are common to all the builds:

+*'''resources'''

+**'''workspace.template.zip''' : defines an empty workspace with settings suitable for the Papyrus build (disables the missing PDE API baseline errors)

+*'''serverConfig :''' (after each modification, the scripts in this directory must be copied into "/opt/public/modeling/mdt/papyrus" where they run : commit the script and run /opt/public/modeling/mdt/papyrus/updateServerSideScripts.sh)

 **'''addDownloadStats.sh :''' script that enables download statistics on an update site

-**'''addDownloadStats.xsl :''' XSL transformation that enables download statistics on an update site (it contains the list of features that must be part of the stats)

-**'''cronPromote.sh :''' a script that runs as a cron on build.eclipse.org to publish the latest nightly

-**'''release_0.8.sh :''' used to publish a release

+**'''addDownloadStats-main.xsl :''' XSL transformation that enables download statistics on a "main" update site (it contains the list of significant plug-ins for the stats)

+**'''addDownloadStats-extra.xsl :''' XSL transformation that enables download statistics on a "extra" update site (it contains the list of significant plug-ins for the stats)

+* '''addToComposite.sh''' : script to add a child update site to a composite update site definition (calls addToComposite.xsl)

+* '''addToComposite.xsl''' : XSL transformation to add a child update site to a composite update site definition

+* '''backupHudsonJobs.sh''' : retrieves the configuration files for all the Papyrus Hudson jobs, and copies them into the hudsonJobs folder (configure a [http://linuxproblem.org/art_9.html password-less ssh login] to avoid having to type your password 10 times in a row). Run this script every time you make changes to the Hudson job configurations, in order to keep a versioned backup of these changes.

+**'''cronPromoteMonitor.sh :''' a script that runs as a cron on build.eclipse.org to publish the latest nightlies (main, extra and tests). It runs cronPromote.sh and sends a mail if this script failed.

+**'''cronPromote.sh :''' the script that does the actual work for cronPromoteMonitor.sh

+**'''promoteFunctions.sh :''' helper functions for the publishing scripts

+**'''manualPromote.sh :''' this is an interactive script that can be started by a Papyrus committer to publish a build into the Papyrus downloads and update site

+**'''release_0.8.sh :''' used for publishing 0.8 releases

+**'''updateServerSideScripts.sh''' : run this script from /opt/public/modeling/mdt/papyrus/updateServerSideScripts.sh to update the scripts on the server after committing your changes

 *'''xsl :'''

 **'''psf :''' to build the psf from a Buckminster ''bill of materials''. The BOM is produced by Buckminster when importing all the dependencies, and contains a list of these dependencies.

 ***'''bom2repository.xsl :''' transforms a Buckminster BOM into a list of dependent repositories

@@ -24,22 +57,15 @@ The papyrus releng project is called : '''org.eclipse.mdt.papyrus.releng.buckmin
 ***'''papyrus_bom.xml:''' used for testing the generation of the PSFs

 ***'''repository2subclipse.xsl:''' creates a Subclipse PSF from a repository.xml 

 ***'''repository2subversive.xsl:''' creates a Subversive PSF from a repository.xml 

-**'''build.xml:''' the main ant build script : installs Buckminster, imports the dependencies and the Papyrus projects from SVN, builds the workspace, creates the update site and runs the tests

 **'''content2html.xsl''': creates an index.html with a user-viewable list of all installable Papyrus plug-ins and features

 **'''content2xml.xsl''': creates an index.html with a machine-readable list of all installable Papyrus plug-ins and features

-*'''buckminster.cspec :''' describes the top-level dependencies of the build

-*'''build.cquery :''' describes the root request for the Buckminster import, properties for the import (for example, it indicates that the Papyrus source plug-ins should not be materialized during the import, as they are generated by Buckminster during the build), and references the Buckminster rmap

-*'''build.mspec :''' description for the Buckminster '''materialization''' (i.e. import) of artifacts (plug-ins and features), when building on *.eclipse.org

-*'''local.mspec :''' description for the Buckminster materialization when building locally

-*'''build.rmap :''' should be updated for each release. An EMF-Facet script allows to update it easily using the b3 file. The tag '''<!-- updateFrom -->''' is used by the script. 

-*'''build.properties :''' properties for the build (when building on *.eclipse.org)

-*'''local.properties :''' properties for the build (when building locally)

+

 

 

 == Build process ==

 

 Taking the example of the job papyrus-trunk-nightly:

-* When the Hudson job papyrus-trunk-nightly starts, Hudson begins by doing a checkout of the required folders (which are specified in the job configuration) from the SVN : the "plugins", "features" and "releng" folders are retrieved, and placed under a directory named "sourceTree" in the Hudson workspace.

+* When the Hudson job papyrus-trunk-nightly starts, Hudson begins by doing a checkout of the required folders (which are specified in the [[#Hudson_job.27s_SVN_configuration]]) from the SVN : the "plugins", "features" and "releng" folders are retrieved, and placed under a directory named "sourceTree" in the Hudson workspace.

 * Then the first bash script (from the releng project that was just retrieved from the SVN) is executed : "sourceTree/releng/org.eclipse.mdt.papyrus.releng.buckminster/papyrus-trunk-nightly/build-before.sh". This script does a bit of clean-up and initializes variables for the build.

 * Then the main build script is executed: "sourceTree/releng/org.eclipse.mdt.papyrus.releng.buckminster/papyrus-trunk-nightly/build.xml":

 ** it reads the property file '''build.properties''', which defines settings for the build

@@ -73,16 +99,50 @@ Nightly builds are published automatically to download.eclipse.org.
 

 This part is a bit tricky, as the build server (https://hudson.eclipse.org) and the download server download.eclipse.org are two separate servers, with different access rights. The download server can be accessed by all committers, but the Hudson jobs are launched by a Hudson user that does not have write access to the download server. Thus, publishing results is done in two parts:

 *the Hudson task gathers all results and sends a signal to the download server (basically, writing a signal file on the download server, with information on what to publish and where). 

-*A cron task that runs every 5 minutes on build.eclipse.org (currently setup under user "vlorenzo") compares the timestamp of the signal file to a reference file. When the signal file is more recent than the reference file, the cron task proceeds to some actions: cleaning the download area (leaving for example only the last 5 nightly builds for each version of the plug-ins), and then getting the results provided by the hudson job to copy them in the right places in the download area. The cron task launches the script cronPromoteMonitor.sh located in ''/opt/public/modeling/mdt/papyrus/'' on build.eclipse.org.

+*A cron task runs every 5 minutes on build.eclipse.org (currently setup under user "vlorenzo"), and launches the script cronPromoteMonitor.sh located in ''/opt/public/modeling/mdt/papyrus/'' on build.eclipse.org. This script compares the timestamp of the signal file to a reference file. When the signal file is more recent than the reference file, it proceeds to cleaning the download area (leaving for example only the last 5 nightly builds for each version of the plug-ins), and then getting the results provided by the hudson job to copy them in the right places in the download area.

 

-=== Build chaining ===

+=== configuration of the cron script ===

+The publishing script is started every five minutes ("*/5") to see if there are new builds to publish and publish them.

 

-The publication of papyrus-trunk-nightly triggers the build of papyrus-trunk-extra-nightly and papyrus-trunk-nightly-tests, by using the [http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API Hudson Remote Rccess API], passing it the build id and version as parameters, so that the cronPromote can publish the results of papyrus-trunk-extra-nightly and papyrus-trunk-nightly-tests to the same folder as for the first build.  

+Type this command to edit your crontab on build.eclipse.org:

+ crontab -e

+Then put this single line in the file to start the publishing script every five minutes:

+ */5 * * * * /opt/public/modeling/mdt/papyrus/cronPromoteMonitor.sh

 

+== Build chaining ==

 

-== Publishing a build in the aggregator ==

-The Eclipse simultaneous release train is built with the B3 aggregator. To be part of the aggregation,  

+The publication of papyrus-trunk-nightly triggers the build of papyrus-trunk-extra-nightly, papyrus-trunk-nightly-tests and papyrus-trunk-nightly-3.8-tests, by using the [http://wiki.hudson-ci.org/display/HUDSON/Remote+access+API Hudson Remote Access API], passing it the build id and version as parameters, so that the cronPromote can publish the results of papyrus-trunk-extra-nightly and papyrus-trunk-nightly-tests to the same folder as for the first build.

+

+[[Image:buildChaining.png]]

+

+== Build dependencies ==

+The Hudson jobs papyrus-trunk-nightly-tests, papyrus-trunk-nightly-3.8-tests and papyrus-trunk-extra-nightly depend on the [https://hudson.eclipse.org/hudson/job/papyrus-trunk-nightly/ws/updateSite/ update site] created by the Hudson job papyrus-trunk-nightly.

 

+The dependency appears in the rmap:

+<pre>

+<rm:provider componentTypes="eclipse.feature,osgi.bundle" mutable="false" readerType="p2" source="false">

+  <rm:uri format="{0}">

+    <bc:propertyRef key="papyrus.update.site"/>

+  </rm:uri>

+</rm:provider>

+</pre>

+

+And the variable "papyrus.update.site" is defined in the Hudson job configuration:

+

+[[Image:hudsonUpdateSiteDependency.png]]

+

+== Publishing a build in the aggregator ==

+The Eclipse simultaneous release train is built with the B3 aggregator. To be part of the aggregation, you must add your contribution to the aggregation model:

+* checkout the project org.eclipse.<releaseName>.build from the Eclipse CVS ":pserver:<committerID>@dev.eclipse.org:/cvsroot/callisto"

+* open "mdt-papyrus.b3aggrcon"

+* change the location on this line to point to the build you want to publish in the aggregator:

+ <repositories location="http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/0.9/M4" description="Papyrus">

+* validate the build model : 

+** open "simrel.b3aggr"

+** right-click on the root and choose '''Validate Aggregation'''

+** open the error log and see if everything went OK

+* commit your changes

+* optionally start an [https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/juno.runAggregator/ aggregation build] (the build should start automatically after you commit changes)

 

 == Entering the simultaneous release train ==

 You should indicate that your project follows the Eclipse Train. Go to the Eclipse portal [https://dev.eclipse.org/portal]. In Eclipse Projects, click on '''view''' : 

@@ -174,6 +234,140 @@ The update site directory looks like this:
    features

    plugins

 

-== Retention policy ==

+You can also make a composite child point to a different location. This is useful for moving update sites to archive.eclipse.org transparently (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=349141 bug 349141]).

+

+For example:

+ <child location="http://archive.eclipse.org/modeling/mdt/papyrus/updates/releases/indigo/0.8.0"/> 

+

+see also [http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_(new)]

+

+== Papyrus update sites ==

+The Papyrus update sites are under:

+ http://download.eclipse.org/modeling/mdt/papyrus/updates/...

+corresponding to this directory mounted on build.eclipse.org:

+ /home/data/httpd/download.eclipse.org/modeling/mdt/papyrus/updates/...

+

+The Papyrus update sites follow this layout:

+ releases (folder)

+   helios (composite update site)

+   indigo (composite update site)

+     0.8.0 (update site)

+     0.8.1 (update site)

+   juno (composite update site)

+     0.9.0 (composite update site)

+       main (update site)

+       extra (update site)

+ milestones

+   0.8 (composite update site)

+     SR2_RC1 (update site)

+     SR2_RC2 (update site)

+   0.9 (composite update site)

+     M4 (composite update site)

+     M5 (composite update site)

+       main (update site)

+       extra (update site)

+ nightly

+   indigo (composite update site)

+   juno (composite update site)

+     main (update site)

+     extra (update site)

+

+== Papyrus downloads ==

+The Papyrus download page is:

+http://www.eclipse.org/modeling/mdt/papyrus/downloads/index.php

+

+This page is generated from downloads-common.php and downloads-scripts.php that are defined in the folder "/www/modeling/mdt/papyrus/downloads/" on CVS "dev.eclipse.org:/org.eclipse".

+

+== Download statistics ==

+The statistics are enabled on repositories that are published with manualPromote.sh. This script calls addDownloadStats.sh, and it uses:

+* addDownloadStats-main.xsl for statistics on the main update site

+* addDownloadStats-extra.xsl for statistics on the extra update site

+

+These XSL transformations add the property "p2.statsURI" to the update site metadata, and add a "download.stats" property on a few bundles that are significant for the project's statistics.

+

+The statistics can then be seen on the Eclipse portal (see the documentation below)

+

+See:

+* http://wiki.eclipse.org/Project_Download_Stats

+* http://wiki.eclipse.org/Equinox_p2_download_stats

+

+== Archiving old builds ==

+The download.eclipse.org server only has so much space. So, the webmaster set a 2 GiB quota per project.

+

+To stay under this limit, old builds should be either deleted or moved to archive.eclipse.org.

+

+This must be done in accordance to the Papyrus retention policy.

 TODO: Papyrus should define a retention policy, and link to it in the portal.

 

+See : 

+* http://wiki.eclipse.org/IT_Infrastructure_Doc#Move_files_to_archive.eclipse.org.3F

+

+== Promoting a RC to a release ==

+On the day of the release, the last release candidate build should be renamed. 

+You should rename your release candidate build in "/modeling/mdt/papyrus/downloads/drops/x.y.z/" For example:

+* S201106151305 becomes R201106151305

+* Papyrus-Update-0.9.0RC4.zip becomes Papyrus-Update-0.9.0.zip

+

+There is nothing to rename in the update site, but you should copy the contents of the release candidate update site to the release update site.

+

+For example, copy the contents of:

+ /modeling/mdt/papyrus/updates/milestones/0.9/RC4

+into

+ /modeling/mdt/papyrus/updates/releases/juno/0.9.0

+

+See:

+* http://wiki.eclipse.org/Indigo/Final_Daze

+

+== Hudson job's SVN configuration ==

+

+[[Image:hudsonSvnConfig.png|frame|Hudson SVN Config]]

+

+== Interpreting build errors ==

+The error can sometimes be found at the end of the log, but is often burried deep within megabytes of output (especially when Buckminster is run with the DEBUG log level). So, to find an error, you can search for patterns:

+* '''"ERROR"''' for Buckminster import errors

+* '''"Error: file "''' for compilation errors

+

+=== import errors ===

+ ERROR   [0009] : No suitable provider for component org.eclipse.xyz:osgi.bundle was found in resourceMap [...]

+It means that the import phase done by Buckminster failed because Buckminster could not find plug-in "org.eclipse.xyz" in the rmap. 

+If this is one of your plug-ins, you can fix this error by:

+* adding it to the rmap if it was not already matched by a pattern (regular expression) there

+* making sure that the plug-in has the right name and is in the right location on SVN

+* making sure that the plug-in is contained (indirectly) by the build feature

+If this is a plug-in from another project you depend on, you can fix this error by:

+* making sure you have defined in your rmap the update site from which this plug-in must be found

+* making sure that the locator pattern points Buckminster to the right update site for this plug-in

+* making sure that you depend on the right version of the plug-in (in the referencing project's MANIFEST.MF)

+

+Notice the "[0009]" tag before the error message: it refers to more information at the end of the build log. Search for this number, and you will find something like:

+ INFO:  TAG-ID 0009 = Query for org.eclipse.mdt.papyrus.releng.buckminster:buckminster, path:

+ org.eclipse.mdt.papyrus.releng.buckminster:buckminster$0.9.0.qualifier -> 

+ org.eclipse.xxx:osgi.bundle$0.9.0.qualifier -> 

+ org.eclipse.yyy:osgi.bundle$0.9.0.qualifier -> 

+ org.eclipse.zzz:osgi.bundle$0.9.0.qualifier 

+

+It gives you the dependency chain leading to the plug-in that cannot be resolved. 

+

+=== compilation errors ===

+ Error: file /opt/public/jobs/<jobName>/workspace/buildroot/buckminster.workspace/plugins/<pluginName>/src/<javaClassPath>, line xyz: <javaErrorMessage>

+This is a Java compilation error.

+* Make sure that the code compiles in your workspace

+* Make sure that your development environment contains the same plug-ins with the same versions as the Buckminster build (see buildroot/result/targetPlatform in the Hudson workspace)

+

+=== The Hudson build's workspace ===

+You can see the contents of the Hudson build's workspace on Hudson. For example:

+ https://hudson.eclipse.org/hudson/job/papyrus-trunk-nightly/ws/

+

+At the end of the build, the Hudson workspace contains these files:

+* buildroot : the working directory for the Buckminster build

+** result

+*** output : Buckminster puts what it buildt in this directory

+*** targetPlatform : the target platform that was materialized by Buckminster during the import phase, and that was used during the build. All the 

+** tools

+*** buckminster : the installation of Buckminster that was used for building

+*** director : the p2 director that was used to install Buckminster

+* sourceTree : the Papyrus sources that were checked out from SVN by Hudson

+* tmp/N201201260428 : the temporary folder that was used to create the result zip

+* updateSite : a copy of the update site that was produced by Buckminster. The other Papyrus builds (for extra and tests) use this update site

+* Papyrus-Main.zip : this is the result of the build, packaged in a zip ready to be published by the cron publishing script

+

diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/howToUse.mediawiki b/sandbox/org.eclipse.papyrus.build.documentation/resources/howToUse.mediawiki
index a4fe9de752e..ba6790e7ec6 100644
--- a/sandbox/org.eclipse.papyrus.build.documentation/resources/howToUse.mediawiki
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/howToUse.mediawiki
@@ -1,20 +1,22 @@
-The Papyrus project is built using [[Buckminster]], with this releng project: [https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/releng/org.eclipse.mdt.papyrus.releng.buckminster https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/releng/org.eclipse.mdt.papyrus.releng.buckminster]

-(for the trunk; the branches are build with the corresponding project from the branch).

+The Papyrus project is built using [[Buckminster]], with this releng project:

+https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/releng/org.eclipse.mdt.papyrus.releng.buckminster

+(only for the trunk; the branches are build with the corresponding project from the branch).

 

 This project contains sub-folders containing the Buckminster configuration for each Hudson job. 

 

 == Hudson Jobs ==

 The Papyrus builds are started from Hudson. The following jobs exist currently:

 * papyrus-trunk-nightly : builds the main plug-ins on the trunk of Papyrus

-* papyrus-trunk-nightly-tests : installs the latest Papyrus nightly build and runs the unit tests

+* papyrus-trunk-nightly-tests : installs the latest Papyrus nightly build and runs the unit tests (on Eclipse 4.x)

+* papyrus-trunk-nightly-3.8-tests : installs the latest Papyrus nightly build and runs the unit tests (on Eclipse 3.x)

 * papyrus-trunk-extra-nightly : builds the "extra" plug-ins of Papyrus (on the trunk) 

 * papyrus-trunk-extra-nightly-tests (not implemented yet): installs the latest Papyrus nightly build with extras and runs the unit tests for the extra plug-ins

 * papyrus-0.8-maintenance-nightly : builds the main plug-ins on the branch 0.8 of Papyrus

 * papyrus-0.8-maintenance-nightly-tests : installs the latest Papyrus nightly build for branch 0.8 and runs the unit tests

-* papyrus-0.8-maintenance-nightly : builds the "extra" plug-ins of Papyrus (on branch 0.8) 

-* papyrus-0.8-maintenance-nightly-tests (not implemented yet): installs the latest Papyrus nightly build with extras (branch 0.8) and runs the unit tests for the extra plug-ins

+* papyrus-0.8-maintenance-extra-nightly : builds the "extra" plug-ins of Papyrus (on branch 0.8) 

+* papyrus-0.8-maintenance-extra-nightly-tests (not implemented yet): installs the latest Papyrus nightly build with extras (branch 0.8) and runs the unit tests for the extra plug-ins

 

-See all the currently defined Papyrus jobs on this page : [https://hudson.eclipse.org/hudson/user/vlorenzo/my-views/view/Papyrus https://hudson.eclipse.org/hudson/user/vlorenzo/my-views/view/Papyrus]

+See all the currently defined Papyrus jobs on this page : https://hudson.eclipse.org/hudson/user/vlorenzo/my-views/view/Papyrus

 

 == What is built? ==

 

@@ -82,7 +84,7 @@ These builds can then be seen and downloaded from http://www.eclipse.org/modelin
 === With the script ===

 

 To publish a milestone or release, you can use the manualPromote.sh script on: '''/opt/public/modeling/mdt/papyrus/manualPromote.sh'''

-Then, fill in the parameters in the interactive script, and it will:

+Start this script, and fill in the parameters in the interactive script, and it will:

 * publish the build to the download drops

 * 

 * 

diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonSvnConfig.png b/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonSvnConfig.png
new file mode 100644
index 00000000000..d28ab5d652b
--- /dev/null
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonSvnConfig.png
diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonUpdateSiteDependency.png b/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonUpdateSiteDependency.png
new file mode 100644
index 00000000000..ef2dd7d34dc
--- /dev/null
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/hudsonUpdateSiteDependency.png
diff --git a/sandbox/org.eclipse.papyrus.build.documentation/resources/releng.png b/sandbox/org.eclipse.papyrus.build.documentation/resources/releng.png
index 2398f66e7e4..93bd9d71fd4 100644
--- a/sandbox/org.eclipse.papyrus.build.documentation/resources/releng.png
+++ b/sandbox/org.eclipse.papyrus.build.documentation/resources/releng.png