This is my first time setting up Hudson, and I would like to make trigger assemblies in the following order:
(We use SVN)
- after fixation, but only after there will be no more fixation activity for a certain period of time. I do not want to run the assembly for each commit if they occur during a small time delta. For example, mark a pending build / task in a commit, but wait until some commits occur for some time.
I don’t want to just run the assembly every time period - I need time periods and commit. We also note that the assembly should not occur if the last commit was recently - we need to wait for some inactivity.
I can just complete the daily build. I really squeeze a unique build on every commit. Now Win32 assembly takes from 20 minutes to an hour depending on the machine. When we have cross-platform builds that will also be significant.
I am also open to comments and arguments for creating an assembly on each commit. (Note that one of the developers’s template is to commit several different sets of files - with close interlacing.) I would prefer not to waste all processor cycles and disk space by making an assembly that will be useless / discarded for a minute or two. I also don't think that starting multiple assemblies at the same time (does hudson do this or wait for the assembly to complete) is useful / desirable.
source share