Greetings, Now that BuildHive has been announced, I think we should start using it as the primary place for all Jenkins' plugin CI needs. It's kind of a pain to manage these things for each plugin ourselves at JonJ - http://ci.jenkins-ci.org
I think it also lends itself to us having to be more stable on official JonJ since more and more plugin developers are depending on it to build and test their plugins. This has an inverse effect that JonJ can't be a place to test out more experimental work, as well as other expectations about availability and stability. In addition to being extremely easy to use, BuildHive also will automatically test out pull requests and comment in the GitHub pull request whether the change broke the build. This is totally awesome! I think we may also be able to easily exploit Validated Merge functionality which does roughly the same thing but without the hassle of creating a pull request. The proposal for discussion is to take a snapshot of all our plugin jobs on ci.jenkins-ci.org as an archive. Then delete them from ci.jenkins-ci.org. Utilize BuildHive as the canonical place for Jenkins on Jenkins testing for plugins-only. Continue current usage of ci.jenkins-ci.org for core and forked libs. Comments? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
