Ok. Hopefully have completely fixed our buildbot setup. Now we have the following builders:
[19:23] <tomee-bot> openejb-branch31: idle, last build 1622h15m45s ago: failed compile [19:23] <tomee-bot> openejb-branch32: idle, last build 11132h41m42s ago: failed test [19:23] <tomee-bot> tomee-javaee-api: idle, last build 9m00s ago: failed deploy [19:23] <tomee-bot> tomee-patches: idle, last build 8m16s ago: build successful [19:23] <tomee-bot> tomee-release-branch: idle [19:23] <tomee-bot> tomee-trunk-deploy: idle [19:23] <tomee-bot> tomee-trunk-empty-repo: idle [19:23] <tomee-bot> tomee-trunk-itests: idle, last build 3m22s ago: failed cdi-tomee-webapp-deployer [19:23] <tomee-bot> tomee-trunk-osx: offline [19:23] <tomee-bot> tomee-trunk-ubuntu: building(compiling) [19:23] <tomee-bot> tomee-trunk-win-ibmjdk6: idle [19:23] <tomee-bot> tomee-trunk-win-sunsdk: building(updating) Maintaining our buildbot config has been an incredible pain, so finally I learned some Python and rewrote it. Those of us who have had to deal with it in the past should find it a breath of fresh air. There were soooo many fixed strings not updated, paths that pointed nowhere, and builder names that didn't match the build definition, commenting out a builder or adding a builder was a pain. Some of the build definitions didn't even have schedules anymore and were not used. In general, a pain. Should be much easier now. Before: - https://svn.apache.org/repos/infra/!svn/bc/847059/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf After: - https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomee.conf We also have a builder we could potentially use for each release: [19:23] <tomee-bot> tomee-release-branch: idle This `tomee-release-branch` builder is setup to watch the following path: - http://svn.apache.org/repos/asf/tomee/tomee/branches/release So if we put our release branch there when we make one, we won't have to setup a buildbot builder each time we do a release. -David
