File: control

package info (click to toggle)
buildbot 0.8.12-3.2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 25,220 kB
  • sloc: python: 251,116; ansic: 1,346; makefile: 330; sh: 174; xml: 103
file content (51 lines) | stat: -rw-r--r-- 1,840 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Source: buildbot
Section: devel
Priority: optional
Maintainer: Andriy Senkovych <jolly_roger@itblog.org.ua>
Uploaders: Matthias Klose <doko@debian.org>
Build-Depends: debhelper (>= 7.0.50~),
 python-all-dev,
 python-jinja2 (>= 2.1),
 python-migrate (>= 0.8.0),
 python-mock,
 python-setuptools,
 python-sphinx (>= 1.0.7+dfsg),
 python-twisted (>= 11.0),
 python-dateutil (>= 1.5),
 libaprutil1,
 bash-completion
Homepage: http://buildbot.net
Standards-Version: 3.9.6
X-Python-Version: >= 2.5
Vcs-Browser: https://github.com/buildbot/debian-buildbot
Vcs-Git: git://github.com/buildbot/debian-buildbot.git
Testsuite: autopkgtest

Package: buildbot
Architecture: any
Depends: ${python:Depends}, ${misc:Depends}, ${sphinxdoc:Depends},
 ${shlibs:Depends},
 python-jinja2 (>=2.1),
 python-migrate (>= 0.6.1),
 python-twisted (>= 2.0),
 python-dateutil (>= 1.5),
 dpkg (>= 1.15.4),
 adduser
Recommends: buildbot-slave,
 python-twisted-mail,
 libaprutil1
Suggests: bzr | subversion | cvs | mercurial | darcs | git
Description: system to automate the compile/test cycle
 The BuildBot is a system to automate the compile/test cycle required
 by most software projects to validate code changes. By automatically
 rebuilding and testing the tree each time something has changed,
 build problems are pinpointed quickly, before other developers are
 inconvenienced by the failure. The guilty developer can be identified
 and harassed without human intervention.
 .
 By running the builds on a variety of platforms, developers who do
 not have the facilities to test their changes everywhere before
 checkin will at least know shortly afterwards whether they have
 broken the build or not. Warning counts, lint checks, image size,
 compile time, and other build parameters can be tracked over time,
 are more visible, and are therefore easier to improve.