Test GDB for each new repository commit and report any regressions for it. Test also regressions for user-provided patches.
Regressions get detected by running the thorough GDB testsuite and (a bit fuzzy) comparison of its results against the previous build results.
(optional, can be done by the GDB team) Analyze existing buildbot solutions, we could just deploy one of them:
Mozilla http://buildbot.net ,
GCC testing http://gcc.gnu.org/testing
- a bot in use for GDB in Red Hat by Jan Kratochvil:
Hudson: http://hudson-ci.org/docs/HudsonIntro.pdf last page has some summary of such other existing tools
Compatibility is required with GDB repository in both CVS and GIT.
Support various provided (as rpms, distros or upstream repository branches/tags) GCC versions for building GDB and its testing workload.
Support multiple testing hosts with various architectures. Beaker test system integration must not be required for x86* but it should be supported to be able to cover also other arches.
Support running multi-host testsuite using gdbserver (remote GDB backend).
Properly report kernel crashes of hosts under the test. Associate the kernel crash reports with the GDB workload under test.
(optional) Integration with Fedora/RHEL mock (OS distribution provisioning) and the rpm packaging to test also new Fedora/RHEL builds with it.
(optional) Besides GDB to regression test also binutils.
Supporting other features of existing buildbot solutions.