Next: , Up: Other Tools

5.3.1 sendchange

This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource (see PBChangeSource) running in the buildmaster (by being set in c['change_source']).

     buildbot sendchange --master MASTERHOST:PORT --username USER FILENAMES..

The master and username arguments can also be given in the options file (see .buildbot config directory). There are other (optional) arguments which can influence the Change that gets submitted:

(or option branch) This provides the (string) branch specifier. If omitted, it defaults to None, indicating the “default branch”. All files included in this Change must be on the same branch.
(or option category) This provides the (string) category specifier. If omitted, it defaults to None, indicating “no category”. The category property can be used by Schedulers to filter what changes they listen to.
(or option project) This provides the (string) project to which this change applies, and defaults to ”. The project can be used by schedulers to decide which builders should respond to a particular change.
(or option repository) This provides the repository from which this change came, and defaults to ”.
This provides a (numeric) revision number for the change, used for VC systems that use numeric transaction numbers (like Subversion).
This provides a (string) revision specifier, for VC systems that use strings (Arch would use something like patch-42 etc).
This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument.
This parameter is used to set a property on the Change generated by sendchange. Properties are specified as a name:value pair, separated by a colon. You may specify many properties by passing this parameter multiple times.
This provides the change comments as a single argument. You may want to use --logfile instead.
This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin.