I just want to let everybody know that Ivan and me have succeeded in setting up the
build engine on our Edis host. It is ready for use, stable, and well tuned for our needs.
Small fixes or improvements may be required but I don't expect any bigger problems.
Some background information can be found on our Wiki.
http://wiki.blackboxframework.org/index ... ild_Engine
and
http://wiki.blackboxframework.org/index ... g_Strategy.
Ivan pointed out correctly that using Jenkins would be a tremendous overkill. Doing it via a simple
cron job that activates the build engine periodically serves our needs perfectly.
The current implementation must be seen as a proposal to the center.
I would, however, like to ask the center members to be careful with
alternative suggestions before fully understanding all the concepts and its application to our repository.
The current proposal follows best practices where possible and meaningful while at the same time
it tries to keep simple things simple. I am convinced that it is not easy to come up with a
much better solution by now.
The current solution supports for example building for topic branches as well as for master, it supports
development stages, it provides consistent version information etc. etc.
It also does a rigorous self test before creating a distribution.
There is only one single place (appbuild/AppVersion.txt) where the currently built version is specified.
This information goes automatically to the About dialog, to Dialog.version and to the generated file names.
There is only one single place where new modules must be added to be compiled and distributed and this place
is the well-known file Dev/Docu/Build-Tool.odc. From here the build engine takes the information which
files to compile and in which order.
- Josef
