So the CI choices for Apache are the following:
- Buildbot <http://ci.apache.org/#buildbot> - Continuum <http://ci.apache.org/#continuum> - Gump <http://ci.apache.org/#gump> - Hudson <http://ci.apache.org/#hudson> There is a current discussion on the build list about moving with the name shift of hudson to jenkins. My vote is to go with hudkins [?] because it has been successfully used for .net projects in the past and has plugins to help support that. Nothing personal against python, but there seems to be more material on integration .net builds inside of Hudson. I've also used Hudson in the past so I can vouch that it does a decent job. (This was a while ago, so I can only hope the number of plugins and integration points have increased). I'm going to do a bit more reading on the apache mailing list for builds to see if there is an actual windows slave for hudson/jenkins (which shall henceforth be called hudkins on this list, well at least by me). Obviously the first priority will be getting a build set up and starting simple. However to spark discussion and future planning: Here is a list of other things to include or think about for the build process long term. * fxcop - (this will probably need customized rules for strict java port version) * stylecop - (same) * sandcastle - (building xml comments into documentation). * sandcastle help file builder - (SHFB) * code coverage tool - possibly seeing if we can get a code coverage tool (possibly ncover as they used to give a free license to os projects), * code metrics tool - (i.e. cyclomatic complexity, ndepend used to do the same thing as ncover, thus worth investigating). * gallio test runner vs nunit. (gallio is testing automation tool capable of running various testing frameworks and tools including nunit). * extended msbuild tasks. * mono build. * project structure for the build. ** * insert _____ any other suggestions here. I'll volunteer myself for the boring job of fixing up xml comments so there is some meat and code examples inside xml comments so the documentation generates more than just text and method signatures with type information. After some discussion in the list and unless there is show stopper or killer reason not to go with hudkins. I'll notate the decision the jira and start putting notes in the wiki about the CI. notes: ----------------- ** a common project structure/format or some variant there of, which might be more intuitive for people that have worked on other foss projects. trunk|root /src (source) /lib|vendor (dependencies) /tests (test code) /docs (documentation, architechture, diagrams, notes, etc) /bin (executables - bat, exe, cmd files, etc) root documents (licenses,readme,etc) - Michael
