Hi all, It is a frequently asked question why we didn't use buildbot to test our own github Pull-Requests.
Using buildbot to securely test pull-requests with Buildbot is difficult. As the worker is running the code that anybody can push to you it would be easy for an attacker to take control of our infrastructure. Over the last few months, we have partnered with the fine guys at https://hyper.sh to build a secure and fast solution to test our Github Pull-requests Here is a blog post from hyper people explaining why it is interresting to use hyper for your CI uses, not only for PR https://blog.hyper.sh/serverless-ci-hyper-docker-integration-for-buildbot.html As a result, the buildbot pull-requests have been mostly managed by buildbot_travis on hyper.sh for 3 weeks now. It helps us a lot to get faster and more detailed testing results. [image: Screenshot_2016-10-20_18-15-47.png] Here is a blog and video tutorial I worked on detailing how to deploy your own version in a matter of minutes. Full detailed tutorial is here: https://www.hyper.sh/howto/how-to-use-hyper.sh-to-deploy-your-buildbot.html and the video of me executing it in 20 minutes https://www.youtube.com/watch?v=N8ALf7vKYoQ Hyper team is sponsoring the buildbot open-source project by giving us free credits for running our CI and helping them scale. Please use the following invite to get another $10 credit on top of the $25 welcome credits. This really gives you a lot of playground to start with buildbot on hyper. https://console.hyper.sh/register/invite/e62KM0bdrBF7mW8mKJDJhLqdR6GEJDC6 Have fun with parallel testing with buildbot and hyper! Regards, Pierre
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users