producing a change list from Redmine
|Assignee:||J. Templ||% Done:|
For the upcoming 1.7 release and for further developments a file that contains a change list is needed. The change list can be included in the distribution and/or put on the web. The changes can be downloaded from the Redmine issues as an xml file and converted into an odc file and/or html.
adding a change list automatically when building master. Refs: #112.
ScriptChanges converts the file blackbox_issues.xml into a file BlackBox_<appVersion>_Changes.odc by using the external subsystem Xmlcore. In order to avoid any build problems in case of future incompatible changes we link ScriptChanges statically to Xmlcore and the base BlackBox modules. The resulting file is bbchanges.exe. It is kept unchanged on the build machine and needs to be re-built manually in case of any changes.
The Redmine issues are downloaded via Python in build.py.
In addition some improvements have been applied:
1. 'git checkout', which always reported an error message, is avoided by using option --branch for 'git clone'.
2. Incrementing the buildNumber multiply in case of an error is now avoided.
3. renameLog checks if outputNamePrefix has been set.
4. Since 'git clone' fails sometimes for unknown reasons, it is treated separately in order to find out what the problem is.
Signed-off-by: Josef Templ <email@example.com>
git clone called with option -q. Refs: #112.
suppresses the progress reporting on stderr, which would be
misinterpreted as an error by the build script.