Class Change
source code
I represent a single change to the source tree. This may involve
several files, but they are all changed by the same person, and there is
a change comment for the group as a whole.
If the version control system supports sequential repository- (or
branch-) wide change numbers (like SVN, P4, and Arch), then revision=
should be set to that number. The highest such number will be used at
checkout time to get the correct set of files.
If it does not (like CVS), when= should be set to the timestamp
(seconds since epoch, as returned by time.time()) when the change was
made. when= will be filled in for you (to the current time) if you omit
it, which is suitable for ChangeSources which have no way of getting more
accurate timestamps.
The revision= and branch= values must be ASCII bytestrings, since they
will eventually be used in a ShellCommand and passed to os.exec(), which
requires bytestrings. These values will also be stored in a database,
possibly as unicode, so they must be safely convertable back and forth.
This restriction may be relaxed in the future.
Changes should be submitted to ChangeMaster.addChange() in
chronologically increasing order. Out-of-order changes will probably
cause the web status displays to be corrupted.
|
__init__(self,
who,
files,
comments,
isdir=0,
links=None,
revision=None,
when=None,
branch=None,
category=None,
revlink='
' ,
properties={ } ,
repository='
' ,
project='
' ) |
source code
|
|
|
|
|
|
|
asDict(self)
returns a dictonary with suitable info for html/mail rendering |
source code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
__providedBy__(...)
Object Specification Descriptor |
source code
|
|
|
number = None
|
|
branch = None
|
|
category = None
|
|
revision = None
|
|
__implemented__ = <implementedBy buildbot.changes.changes.Change>
|
|
__provides__ = <zope.interface.declarations.ClassProvides obje...
|
__provides__
- Value:
<zope.interface.declarations.ClassProvides object at 0x130c1d0>
|
|