buildbot-slave 0.8.7p1-1 source package in Ubuntu

Changelog

buildbot-slave (0.8.7p1-1) experimental; urgency=low


  * New upstream release
  * Enable unit testing during build.
  * Introduce config for git-buildpackage: debian/gbp.conf.
  * debian/gbp.conf: use master branch as primary debian branch
  * Add python-twisted-core and python-mock to build-depends to run unit tests
  * debian/control:
    - prettify Depends
    - bump Standards-Version to 3.9.4.0 (no changes required)

 -- Andriy Senkovych <email address hidden>  Mon, 18 Mar 2013 13:01:55 +0200

Upload details

Uploaded by:
Andrii Senkovych
Uploaded to:
Experimental
Original maintainer:
Andrii Senkovych
Architectures:
all
Section:
devel
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Raring: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
buildbot-slave_0.8.7p1-1.dsc 1.2 KiB cf45e37e5cc914d81a55ec665a9b54c54d95cde3f4ed873f432005154c867631
buildbot-slave_0.8.7p1.orig.tar.gz 101.3 KiB bc540ac3a60f3c66ff84ba99e8532b37c4a57888ddee7820fef9ca721791579a
buildbot-slave_0.8.7p1-1.debian.tar.gz 5.8 KiB ef521d98b1d5f8871a1e7610ee42a39447d676ba2013ae15c6c1e7d238455650

Available diffs

No changes file available.

Binary packages built by this source

buildbot-slave: 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.