| | 1 | = Updating QWG Repository Trunk = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | Normal development process for templates is to develop templates in a Quattor configuration database, where you can deploy the new templates in a real (test or production) environment. Only after, you have validated the modification in your environment, you should update the QWG repository. |
| | 7 | |
| | 8 | New or modified templates '''should always''' been committed to the QWG [source:templates/trunk repository trunk] first, never directly in a [source:templates/branches branch] or [source:templates/tags tag]. |
| | 9 | |
| | 10 | It is quite important not to break the history when a template is moved from one location to another or removed. And the trunk is not a direct copy of a real repository. To help updating the trunk from a real Quattor configuration database, you should use [source:templates/tools/directory_sync directory_sync] tool. '''This tool must be run from a local workspace of QWG [source:templates/trunk repository trunk]'''. This tool updates a trunk directory with the contents of a specified source, doing the following : |
| | 11 | * Removes all `.tpl` files from the destination directory (the directory to update). |
| | 12 | * Copy all .tpl files from the source directory (built by appending destination directory name to source directory root) |
| | 13 | * Show the differences with `svn status` |
| | 14 | |
| | 15 | As you run this tool from a SVN workspace, you always have the opportunity to do a `svn revert` in case things went wrong... |
| | 16 | |
| | 17 | You need to fix manually the unexpected differences. Unexpected differences are all the templates that existed in the repository but no longer exist in the local workspace or all the templates copied from the source but not registered in the repository. There are 3 situations : |
| | 18 | * A template has been renamed or moved. In this case, you should revert the change for this template, do the relevant `svn mv` and rerun `directory_sync` to avoid breaking the template modification history. |
