| 26 | | QWG templates can be checked out using `svn co` command directly or using [source:templates/trunk/tools/check-compile.sh check-compile.sh] script. The script allows to download both a vanilla SCDB and a specific version of the templates. It is then possible to compile the examples provided with the templates to assess they work properly before integrating them in your production SCDB. |
| | 26 | QWG templates can be checked out using `svn co` command directly or using [source:templates/trunk/tools/check-compile.sh check-compile.sh] script. The script allows to download both a vanilla SCDB and a specific version of the templates. It is then possible to compile the examples provided with the templates to assess they work properly before integrating them in your production SCDB. An example of using [source:templates/trunk/tools/check-compile.sh check-compile.sh] to check out glite 3.1 branch is (`-D` is necessary to be able to do `svn update later`): |
| | 27 | {{{ |
| | 28 | check-compile.sh -D -d /qwg/templates gLite-3.1 |
| | 29 | }}} |
| | 30 | |
| | 31 | One gLite branch contains the template for one specific version of gLite, the OS templates and the other standard templates. Even though present in all branches, the OS templates and the other standard templates are identical in all gLite branches. |
| | 32 | |
| | 33 | If you need the templates for several different versions of gLite, there is no need to do a full separate checkout of every gLite version. Instead, just download one (try to use the most actively developped) with [source:templates/trunk/tools/check-compile.sh check-compile.sh] and then add the templates for the other version using the commands below (they are an example to add gLite 3.2 support, customize to your specific need): |
| | 34 | {{{ |
| | 35 | cd /qwg/templates |
| | 36 | svn propset svn:externals 'glite-3.2 https://svn.lal.in2p3.fr/LCG/QWG/templates/branches/gLite-3.2/grid/glite-3.2' cfg/grid/ |
| | 37 | svn update cfg |
| | 38 | }}} |
| | 39 | |
| | 40 | Then, every time you issue `svn update cfg`, you'll get the last version of all the standard templates for all the gLite versions you added. And you can use the procedures described in the relevant [wiki:/Download/QWGTemplates/Install#Upgradinganexistingrepository documentation] to upgrade your production SCDB. |
| | 41 | |
| | 42 | You can also use `svn switch` if you would like to switch the OS templates and the other standard templates to those provided by another branch. This may be necessary as the most recent changes to these templates is not necessarily merged into all branches at the same time (but the most recent version always work with all the branches). |
