Ticket #539 (new enhancement)
add a simpler change notification protocol
| Reported by: | ipv6guru | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.8.+ |
| Version: | 0.7.10 | Keywords: | |
| Cc: | kovarththanan.rajaratnam@… |
Description
I'm thinking that there are environments where it might be useful to have a simpler change-notification protocol, one that doesn't require Twisted or BuildBot to be installed on the VC repository machine, possibly not even Python. It would involve an RFC822-style block of text, with filenames and user names in headers, and the change comments in the body. The sender would open up a TCP socket to the buildmaster and then just send this block to it.
This would let you write a change-notification sender as a shell script that constructs the file and dumps it into netcat.
The receiver (probably named buildbot.changes.tcp or something) would be configured with a TCP port to listen on. You'd want a password of some sort, except that of course they'd all be sent in a plaintext 'Password:' header, and they'd be visible to most VC users. It might make more sense to configure a list of IP addresses from which connections would be accepted, so the admin could just list the repository machine on the list.
This might make it possible to have the sf.net CVS repository machines trigger builds. I'm not sure they are capable of making TCP connections to the outside world, however. Submitted: Brian Warner ( warner ) - 2005-05-22 10:22
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Moved from sourceforge