Testributor Blog parallel posts, distributed thoughts and more

Previously on Testributor

New features

These are new features and funcionality we added last week:

Status notification on Github Pull Requests

When a tracked branch has an open Pull Request on Github, the status of the last build is now visible directly from the Github Pull Request.

Worker groups

Every worker needs access to the project repository on Github. Previously, all workers used the same credentials to access the code. Revoking access from only one (or some) workers was not possible with this setup.

Now the users can create “Worker Groups”. Each group has its own credentials to access both Testributor and Github. When a new group is created, we upload a fresh SSH key on the project’s deploy keys section on Github.

Now every group of workers belonging to the same person (e.g. a developer on the team) can have its own credentials, which can be revoked without breaking access for the rest of the workers.

Users can create worker groups in “Settings -> Worker setup” page.

Aggregated results in Build pages

Until now the users could see the number of passing/failing test jobs only through the progress bar on the top of the Build page. We added a textual summary to make the number of passed/failed jobs always visible.


The most important bugs fixed are:

Degraded performance due to server configuration

Left-over configuration from past tests resulted in poor performance due to insufficient database connections. This has been corrected and the performance is back to normal.