Class ChangeManager

source code

 twisted.application.service.Service --+    
                                       |    
twisted.application.service.MultiService --+
                                           |
                                          ChangeManager

This is the master-side service which receives file change notifications from a VCS. It keeps a log of these changes, enough to provide for the HTML waterfall display, and to tell temporarily-disconnected bots what they missed while they were offline.

Change notifications come from two different kinds of sources. The first is a PB service (servicename='changemaster', perspectivename='change'), which provides a remote method called 'addChange', which should be called with a dict that has keys 'filename' and 'comments'.

The second is a list of objects derived from the buildbot.changes.base.ChangeSource class. These are added with .addSource(), which also sets the .changemaster attribute in the source to point at the ChangeMaster. When the application begins, these will be started with .start() . At shutdown time, they will be terminated with .stop() . They must be persistable. They are expected to call self.changemaster.addChange() with Change objects.

There are several different variants of the second type of source:

• buildbot.changes.mail.MaildirSource watches a maildir for CVS commit mail. It uses DNotify if available, or polls every 10 seconds if not. It parses incoming mail to determine what files were changed.
• buildbot.changes.freshcvs.FreshCVSSource makes a PB connection to the CVSToys 'freshcvs' daemon and relays any changes it announces.