Modification Reader Task¶
This tasks makes it possible to read back modifications made by the Modification Writer Task.
Version¶
Available from version 1.4
Examples¶
Minimalist example
1<modificationReader />Full example
1<modificationReader>
2 <deleteAfterRead>true</deleteAfterRead>
3 <filename>last-mods.xml</filename>
4 <path>mods-path</path>
5</modificationReader>Configuration Elements¶
| Element | Description | Type | Required | Default | Version |
| deleteAfterRead | Delete the files after they have been read. | Boolean | No | false | 1.4 |
| description | Description used for the visualisation of the buildstage, if left empty the process name will be shown. | String | No | The task/publisher name. | 1.5 |
| dynamicValues | The dynamic values to use for the task. | Dynamic Values array | No | None | 1.5 |
| environment | A set of environment variables set for commands that are executed. Each variable should be specified as . |
Environment Variable array | No | ||
| filename | The filename pattern for the file containing the modifications. CCnet with search in the path for files starting with this filename, and having the same extention. For example when filename is set to modifications.xml, ccnet will search for files like so: modifications\*.xml | String | No | modifications.xml | 1.4 |
| path | The directory to search the xml file(s) in. | String | No | Project Artefact Directory | 1.4 |
Notes¶
2 projects in CCNet
1) is a project that does the compile, test, ... stuff, and also writes the modifications using the ModificationWriterTask be sure to set the appendTimeStamp of the modificationWriter to true
2) is a project that deploys the result of project 1
--> copies it to other servers, updates source control (binary references like a framework), ...
The reason for a second project is that this can be done on releases of milestones of project 1
The ModificationReaderTask can now easily read the modification file(s) made by project one, into it's own integration, making it possible that these can be used by the existing tasks/publishers of ccnet for project 2
It is best to place the modificationreader in the prebuild section, so all the other tasks / publisers know the read modifications also.
It is adivisable to keep these configuration elements of the modificationWriter and the modificationReader the same.
Automatically Generated¶
Documentation generated on Monday, 26 May 2014 at 7:18:04 AM