A build cop monitors the continuous integration system, reports build and test failures, and farms out work to resolve issues. The role of build cop rotates on a weekly basis between OSRF developers.
A build cop:
Sets their email address to the Jenkins alias. Jenkins will send build notifications to this email address.
Actively monitors the build reports for failures. At a minimum this should be done hourly.
Notify another OSRF developer to create an issue for a failure. The build cop should maintain a rotating list of developers who receive these requests. The build cop should send a link to the failure, and a short description, such as failing test name, of the problem.
- Search for existing issues. Good keywords are "flaky", and test names. If you find an existing issue, rename the title to include "Build Cop".
- The developer assigned to create an issue should analyze the build, and create an issue with a title that has the "Build Cop" prefix.
- The issue should be assigned to the person who broke the build or test. Do not assign a person if a culprit cannot be identified.
- The person assigned to the issue should work to resolve the issue ASAP. Volunteers should step forward to handle unassigned issues.
Send out a daily report about the build status, and create an entry on this wiki (see the report list below).
Sent out a weekly report on Friday that summarizes the build status over the past week.