You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2021. It is now read-only.
I tend to think this would be even more important than tackling the JenkinsRole; Buildbot is a very powerful and flexible Continuous Integration system, and in my experience it uses less than 10x the memory that Jenkins uses to run, but the bad side is that Buildbot is a pain to configure.
So I guess that easing the configuration part would be a nice gift for the provy users that want to use it to setup a CI server.
I think it's best if we tackle issues with infrastructure first, like security, programming languages (PHP, Java, etc), webservers (like tomcat or nginx+php) and stuff like that.
A CI Server is a VERY specific application, I think.
Create a BuildbotRole to provide a basic Buildbot CI installation (maybe defining master and slave config files to be put in the server as well)
The text was updated successfully, but these errors were encountered: