Previously on Testributor
Its been a while since our last changelog post, but we had quite much going on. Here it goes:
Open source projects
Until now all projects on Testributor were private. Only participants could see the build results and the rest of the project’s pages. Now when you add a new project from a public repo, the project will be public by default on Testributor too. That means, any user, logged in or not, will be able to visit the build result pages. They will not be able to see the project’s settings or any of the administrative pages of your project.
We hope this feature will make it easier for open source projects to use Testributor and benefit from the increased performance potentials. Keep in mind that all open source projects can use Testributor for free, for ever with no limit to the number of workers.
Open source projects already have free CI options, but none of them allows free unlimited parallel jobs. We are aware of the special needs of open source and this is just a small step towards building the best CI for open source. If you try Testributor on an open source project, we would really love to listen to your feedback. You will help us build a better service for the community.
Since we support open source projects, we couldn’t go without supporting status badges. Our badges are Shields.io based so they integrate beautifully with the rest of your badges. You can read more on our documentation.
Bare repository support
Until now only projects hosted on GitHub or Bitbucket could be connected with Testributor. This meant that our users had a better overall experience since we supported webhooks and Pull Request statuses, but it also meant that they had to grant us access to their GitHub/Bitbucket account. Also users using other platforms (like Gitlab, Upsource etc) and users with a bare git repository had no way to use our platform.
This is no longer the case, since we now support any Git repository. To use this feature, simply select the “Bare repo” option on the new project wizard. You will have to provide the repository url and an SSH private key which has access to this repository. We store nothing on your bare repository so there are no automatic hooks for branch tracking. You can trigger a new build through the UI and we will soon release a CLI tool, which will let you achieve the same thing through the command line (among other things).
We changed the look and feel of our Dashboard and we also improved the UX. Some usability problems became obvious over time and we hopefully solved some of these issues in this iteration. We will improve it more during the following weeks.
Some users needed to change the default directory on which the project is cloned on the workers, to make is easier to import some libraries. You can now achieve this by setting the TESTRIBUTOR_PROJECT_DIRECTORY variable to the full path of the directory you want to use as the root of your project. Take care not to overwrite any important directories. The worker won’t prevent you from doing so.