Log message:
py-buildbot: updated to 1.5.0

v1.5.0:
Bug fixes
Fix the umask parameter example to make it work with both Python 2.x and 3.x.
Fix build-change association for multi-codebase builds in the console view..
Fixed builders page doesn't list workers in multi-master configuration
Restricted groups added by :py:class:~buildbot.www.oauth2.GitHubAuth's
getTeamsMembership option to only those teams to which the user belongs.
Previously, groups were added for all teams for all organizations to which
the user belongs.
Fix 'Show old workers' combo behavior.

Features
GitHub teams added to a user's groups by
:py:class:~buildbot.www.oauth2.GitHubAuth's getTeamsMembership option
are now added by slug as well as by name. This means a team named "Bot
Builders" in the organization "buildbot" will be added as both \ 
buildbot/Bot Builders and buildbot/bot-builders.
Make urlText renderable for the
:py:class:~buildbot.steps.transfer.FileUpload build step.
Added noticeOnChannel option to :bb:reporter:IRC to send notices
instead of messages to channels. This was an option in v0.8.x and removed in
v0.9.0, which defaulted to sending notices. The v0.8.x default of sending
messages is now restored.

Reverts
Reverted: Fix git submodule support when using sshPrivateKey and sshHostKey \ 
because it broke other use cases
In order to have this feature to work, you need to keep your master in 1.4.0, \ 
and make sure your worker buildbot.tac are installed in the same path as your \ 
master.

v1.4.0:
Bug fixes
Fix Build.getUrl() to not ignore virtual builders.
Fix git submodule support when using sshPrivateKey and sshHostKey
settings by passing ssh data as absolute, not relative paths.
Fixed :bb:step:P4 for change in latest version of p4 login -p.
:py:class:buildbot.reporters.irc.IrcStatusBot no longer encodes messages
before passing them on to methods of its Twisted base class to avoid posting
the repr() of a bytes object when running on Python 3.

Features
Added new :bb:step:GitPush step to perform git push operations.
Objects returned by :ref:renderer now are able to pass extra arguments to
the rendered function via withArgs method.

Test Suite
Test suite has been improved for readability by adding a lot of inlineCallbacks
Fixed tests which didn't wait for assertFailure's returned deferred.
The test suite now runs on Python 3.7 (mostly deprecation warnings from \ 
dependencies shut down)

Log message:
py-buildbot: updated to 1.3.0

Buildbot 1.3.0

Bug fixes
buildbot-worker docker image no longer use pidfile. This allows to auto-restart \ 
a docker worker upon crash.
GitLab v3 API is deprecated and has been removed from http://gitlab.com, so we \ 
now use v4.

Features
-Git now supports sshHostKey parameter to specify ssh public host key for fetch \ 
operations.
-Git now supports sshPrivateKey parameter to specify private ssh key for fetch \ 
operations.
-GitPoller now supports sshHostKey parameter to specify ssh public host key for \ 
fetch operations. This feature is supported on git 2.3 and newer.
-GitPoller now supports sshPrivateKey parameter to specify private ssh key for \ 
fetch operations. This feature is supported on git 2.3 and newer.
Github hook token validation now uses hmac.compare_digest() for better security

Deprecations and Removals
Removed support for GitLab v3 API ( GitLab < 9 ).

Buildbot 1.2.0

Bug fixes
Don’t schedule a build when a GitLab merge request is deleted or edited
Add GitLab source step; using it, we now handle GitLab merge requests from forks \ 
properly
Fixed a bug in MailNotifier’s createEmail method when called with the default \ 
builds value which resulted in mail not being sent.
Fixed a Github crash that happened on Pull Requests, triggered by Github \ 
Web-hooks. The json sent by the API does not contain a commit message. In \ 
github.py this causes a crash, resulting into response 500 sent back to Github \ 
and building failure.
Speed up generation of api/v2/builders by an order of magnitude.

Improved Documentation
Added examples/gitlab.cfg to demonstrate integrating Buildbot with GitLab.

Features
ForceScheduler Parameters now support an autopopulate parameter.
ForceScheduler Parameters ChoiceParameter now correctly supports the strict \ 
parameter, by allowing free text entry if strict is False.
Allow the remote ref to be specified in the GitHub hook configuration
Added callable to p4 source that allows client code to resolve the p4 user and \ 
workspace into a more complete author. Default behaviour is a lambda that simply \ 
returns the original supplied who. This callable happens after the existing \ 
regex is performed.

Log message:
py-buildbot*: updated to 1.1.1

Bug fixes
* Fix issue which marked all workers dis-configured in the database every 24h
* The :bb:reporter:MailNotifier no longer crashes when sending from/to email
  addresses with "Real Name" parts (e.g., John Doe \ 
<john.doe@domain.tld>).
* Corrected pluralization of text on landing page of the web UI

Improved Documentation
* Corrected typo in description of libvirt
* Update sample config to use preferred API

Misc Improvements
* Home page now contains links to recently active builders

Log message:
py-buildbot-www: TEST_DEPENDS -> BUILD_DEPENDS

setup.py checks for mock's existence and does not build if it's not there.

While here, USE_LANGUAGE -> USE_LANGUAGES.

Log message:
py-buildbot: updated to 1.1.0

Buildbot 1.1.0:

Deprecations and Removals:
Removed ramlfication as a dependency to build the docs and run the tests.

Bug fixes:
Fixed buildrequests API doesn’t provide properties data
Fix missing owner on builder build table
Include hipchat as reporter.
Fix encoding issues of commands with Windows workers
Fixed Relax builder name length restriction
Fix the configuration order so that services can actually use secrets
Partially fix Builder page should show the worker information

Features:
Added the defaultProperties parameter to builders.
When a build step has a log called “summary” (case-insensitive), the Build \ 
Summary page will sort that log first in the list of logs, and automatically \ 
expand it.

Buildbot 1.0.0:

Despite the major version bump, Buildbot 1.0.0 does not have major difference \ 
with the 0.9 series. 1.0.0 is rather the mark of API stability. Developers do \ 
not foresee a major API break in the next few years like we had for 0.8 to 0.9.

Starting with 1.0.0, Buildbot will follow semver versioning methodology.

Bug fixes:
Cloning Git repository with submodules now works with Git < 1.7.6 instead of \ 
failing due to the use of the unsupported --force option.
GitHub hook now properly creates a change in case of new tag or new branch. \ 
GitHub changes will have the category set to tag when a tag was pushed to easily \ 
distinguish from a branch push.
Fixed issue with Master.expireMasters not always honoring its forceHouseKeeping \ 
parameter.
Fixed issue with steps not correctly ending in CANCELLED status when interrupted.
Fix maximum recursion limit issue when transferring large files with LocalWorker \ 
(issue:3014).
Added an argument to P4Source that allows users to provide a callable to convert \ 
Perforce branch and revision to a valid revlink URL. Perforce supplies a p4web \ 
server for resolving urls into change lists.
Fixed issue with buildbot_pkg` not hanging on yarn step on windows
Fix issue with workers notify_on_missing not able to be configurable as a single \ 
string instead of list of string
Fixed Builder page should display worker name instead of id

Features:
Add capability to override the default UI settings
All Reporters have been adapted to be able to use Secret. SVNPoller has been \ 
adapted to be able to use Secret.
Implement support for Bitbucket Cloud webhook plugin in BitbucketCloudEventHandler
The owners property now includes people associated with the changes of the build
The repo source step now syncs with the --force-sync flag which allows the sync \ 
to proceed when a source repo in the manifest has changed.
Add support for compressing the repo source step cache tarball with pigz, a \ 
parallel gzip compressor.

Log message:
py-buildbot: updated to 0.9.14

Buildbot 0.9.14:

Bug fixes
- Compile step now properly takes the decodeRC parameter in account
- Fix duplicate build requests results in
  :py:class:`~buildbot.db.buildrequests.BuildRequestsConnectorComponent` when
  querying the database
- :py:class:`~buildbot.changes.gitpoller.GitPoller` now accepts git branch
  names with UTF-8 characters
- Fixed inconsistent use of `pointer` style mouse cursor by removing it from
  the `.label` css rule and instead creating a new `.clickable` css rule which
  is used only in places which are clickable and would not otherwise
  automatically get the `pointer` icon, for example it is not needed for
  hyper-links.
- Rebuilding with the same revision now takes new change properties into
  account instead of re-using the original build change properties
- Worker authentication is now delayed via a DeferredLock until Buildbot
  configuration is finished. This fixes UnauthorizedLogin errors during
  buildbot restart
- Fixes python3 encoding issues with Windows Service

Features
- new :ref`badges` plugin which reimplement the buildbot eight png badge
  system.
- In progress worker control API. Worker can now be stopped and paused using the UI.
  Note that there is no UI yet to look the status of those actions.
- Make maximum number of builds fetched on the builders page configurable.
- Include `context` in the log message for `GitHubStatusPush`
- On 'Builders' page reload builds when tags change.
- Give reporters access to master single in renderables. This allows access to
  build logs amongst other things
- Added possibility to check www user credentials with a custom class.

Log message:
py-buildbot-www: fix build

Fix typo in BUILD_DEPENDS line and add missing build dependency.

Log message:
Add py-buildbot-www-0.9.11:

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.

This package contains the web frontend component.