+
+In order to use PIPOL you have to create your account here: http://pipol.inria.fr/
+
+\subsection xps_dev_guide_pipol_general What is PIPOL?
+
+The PIPOL platform is a porting, testing and compilation cluster. It hosts several hardware and software
+architectures to perform its work. An user can reserve a resource (a specific hardware, an operating system...)
+to be used interactively or automatically (with a "Nightly Builds" system) for software testing.
+
+\subsection xps_dev_guide_pipol_frontend From PIPOL frontend
+
+You first need to be connected into pipol ssh.
+\verbatim
+user@caraja:~$ ssh pipol.inria.fr
+Linux pipol-server 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC 2009 x86_64
+***************************************************************************
+* You are just logged-on the PIPOL platform server *
+* You can find some documentation about porting works on the platform *
+* on the PIPOL's web site: http://pipol.inria.fr/docs/ *
+* To report bugs you can write to: pipol-sysadm@lists.gforge.inria.fr *
+***************************************************************************
+
+
+user@pipol:~$
+\endverbatim
+Then you can see pipol images availables for deployment
+
+\verbatim
+user@pipol:~$ pipol-sub si
+ amd64_2010-linux-centos-5.dd.gz
+ amd64_2010-linux-debian-squeeze.dd.gz
+ amd64_2010-linux-debian-testing.dd.gz
+ amd64_2010-linux-fedora-core13.dd.gz
+ amd64_2010-linux-fedora-core14.dd.gz
+ amd64_2010-linux-fedora-core16.dd.gz
+ amd64_2010-linux-ubuntu-lucid.dd.gz
+ amd64_2010-linux-ubuntu-maverick.dd.gz
+ amd64_2010-linux-ubuntu-natty.dd.gz
+ amd64_kvm-linux-debian-lenny
+ amd64_kvm-linux-debian-testing
+ amd64_kvm-windows-7
+ amd64-linux-centos-5.dd.gz
+ amd64-linux-debian-etch.dd.gz
+ amd64-linux-debian-lenny.dd.gz
+....
+ i386-linux-ubuntu-lucid.dd.gz
+ i386-linux-ubuntu-maverick.dd.gz
+ i386-linux-ubuntu-natty.dd.gz
+ i386-linux-ubuntu-precise.dd.gz
+ i386_mac-mac-osx-server-leopard.dd.gz
+ i386-unix-freebsd-7.dd.gz
+ i386-unix-opensolaris-10.dd.gz
+ i386-unix-opensolaris-11.dd.gz
+ i386-unix-solaris-10.dd.gz
+ ia64-linux-debian-lenny.dd
+ ia64-linux-debian-squeeze.dd
+ ia64-linux-fedora-core9.dd
+ ia64-linux-redhatEL-5.0.dd
+ x86_64_mac-mac-osx-server-snow-leopard.dd.gz
+ x86_mac-mac-osx-server-snow-leopard.dd.gz
+\endverbatim
+
+You can also see available architectures on host name:
+\verbatim
+navarro@pipol:~$ pipol-sub sa
+=================================================================
+ Availables architectures:
+=================================================================
+
+pipol18
+:i386_2010:amd64_2010:
+pipol19
+:i386_2010:amd64_2010:
+pipol20
+:i386_2010:amd64_2010:
+pipol1
+:i386:amd64:
+pipol2
+:i386:amd64:
+pipol3
+:i386:amd64:
+pipol4
+:i386:amd64:
+pipol5
+:i386:amd64:
+pipol6
+:i386:amd64:
+pipol7
+:i386:amd64:
+pipol8
+:i386:amd64:
+pipol14
+:i386_kvm:amd64_kvm:
+pipol15
+:i386_kvm:amd64_kvm:
+pipol16
+:i386_kvm:amd64_kvm:
+pipol17
+:i386_kvm:amd64_kvm:
+pipol11
+:i386_mac:x86_mac:
+pipol10
+:ia64:
+pipol9
+:ia64:
+pipol12
+:x86_64_mac:
+\endverbatim
+
+When you have choose your image and host (not necessary) you deploy with command line:
+
+pipol-sub esn \<image name\> \<host-name\> \<deployment-time\>
+\verbatim
+user@pipol:~$pipol-sub esn amd64_2010-linux-ubuntu-maverick.dd.gz pipol20 02:00
+user@pipol:~$ssh pipol20
+\endverbatim
+
+You can now make all your tests.
+
+\subsection xps_dev_guide_pipol_home From a computer
+
+You have to renseign to simgrid configuration your pipol login.
+\verbatim
+$ cmake -Dpipol_user=user .
+\endverbatim
+
+Then you have two kind of command:
+\li make \<image-name\>
+\verbatim
+$ make amd64_2010-linux-ubuntu-maverick
+\endverbatim
+This command copy your local simgrid directory to pipol and execute a configure, make and ctest.
+
+\li make \<image_name\>_experimental
+\verbatim
+$ make amd64_2010-linux-ubuntu-maverick_experimental
+\endverbatim
+Same as previous but report into cdash
+
+You can also see all available images from pipol
+\verbatim
+$ make pipol_test_list_images
+\endverbatim
+
+
+\section xps_dev_guide_cdash How to report tests in cdash?
+
+Reporting experiment in cdash is very easy because it is done by ctest.
+
+The easier way is to execute command line "ctest -D Experiemntal" in build directory. More option is available by ctest:
+\verbatim
+ ctest -D Continuous
+ ctest -D Continuous(Start|Update|Configure|Build)
+ ctest -D Continuous(Test|Coverage|MemCheck|Submit)
+ ctest -D Experimental
+ ctest -D Experimental(Start|Update|Configure|Build)
+ ctest -D Experimental(Test|Coverage|MemCheck|Submit)
+ ctest -D Nightly
+ ctest -D Nightly(Start|Update|Configure|Build)
+ ctest -D Nightly(Test|Coverage|MemCheck|Submit)
+ ctest -D NightlyMemoryCheck
+\endverbatim
+
+If you want to have a code coverage, please add option on simgrid.
+\verbatim
+$ cmake -Denable_coverage=ON .
+$ ctest -D ExperimentalStart
+$ ctest -D ExperimentalConfigure
+$ ctest -D ExperimentalBuild
+$ ctest -D ExperimentalTest
+$ ctest -D ExperimentalCoverage
+$ ctest -D ExperimentalSubmit
+\endverbatim
+