adding a buildbot to watch CI's and do rebuilds 'in arrears' once all commits are in
The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure
Blueprint information
- Status:
- Complete
- Approver:
- Denis Silakov
- Priority:
- Essential
- Drafter:
- Jeff Johnson
- Direction:
- Approved
- Assignee:
- Andrey Ponomarenko
- Definition:
- Obsolete
- Series goal:
- Accepted for 5.3
- Implementation:
-
Needs Infrastructure
- Milestone target:
- None
- Started by
- Jeff Johnson
- Completed by
- Jeff Johnson
Related branches
Related bugs
Sprints
Whiteboard
RPM "continuous integration" is currently running on a buildbot master at
http://
The slave is currently running on the same machine. A second slave
on wareham.jbj.org has been added. Other slaves, and more flexible
per-slave configuration is needed.
The daemons need initscript/cron startup somehow; manual start currently.
Additional platforms (and slaves) need to be prioritized and added.
The scheduler is currently a heartbeat: better triggering needs to be devised.
The existing "make test" mechanism is fine for RPM CI. There are also
the Install-FOO and Verify-FOO targets that need to be turned on for
distro-level automated CI.
The ISPRAS "shallow" testing needs to be enabled when ready.
The latest released version of a buildbot SHOULD be used to
simplify configuration.
LCOV/GCOV for rpm-5.4.5 (or later) needs to be undertaken to assess
test coverage, and forward progress when ISPRAS tests are enabled.
(older comments)
The buildbot process needs to be changed to use rpmbuild, not make, as process "bricks".
There's some feeble scripts in buildbot.
See: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
