User: Zhimin Wang | User: Chinua Iloabachie | User: Maureen Kelly | User: Paul J. Morris | User:
Discussed nightly builds. Possible goal to set up maven on fp server at HUH, and use maven there to do nightly build. Alternate to . Looked at steps in Short term set up of ant build run nightly by cron on umbfp server.
Planned out nightly build process. In the short term, to use cron job to get current copy of code from the repository, run an ant build script (or several), with output going to a text file nightlybuildreport.txt which then gets checked back into the repository in the same directory as the build file.
Investigated nightly build capabilities of googlecode, sourceforge, and other public repositories:
- Gnu Savannah http://savannah.nongnu.org/userguide/ and Gna! http://gna.org/userguide/ Don't appear to include build, just version control, bug tracking, and task tracking.
- Launchpad https://launchpad.net/+tour/index Likewise, version control, bug tracking, task (specification) tracking, translation management, and automated Ubuntu package management.
- code.google.com not directly possible, but there is a form of build monitoring with Hudson. Maureen notes:
We might want to consider Hudson as part of "continuous integration" rather than the nightly builds, it might serve our purposes. It seems to be a web-based build monitoring tool. Rather than get email notification (though apparently Hudson can be configured to do that as well), we'd all monitor the Hudson page.
On which Bob comments:Looks nice. There's good news and bad news about continuous builds, though. The good news is that it is more easily insured that the trunk is always buildable. That's the bad news too, because it discourages using the trunk as a backup, giving you access to intermediate work of codevelopers in ways that you can use while they are tinkering. Probably the advantages outweigh disadvantages, but it requires good habits of at least frequently keeping your code buildable. There may be policy issues of whether "buildable" also means "deployable" for services. That kind of consideration is something John Graybeal would have a lot of experience with. This argues towards nightly or otherwise regular builds rather than continuous.
- sourceforge has lots of options and optional packages available http://sourceforge.net/apps/trac/sourceforge/wiki/Hosted%20Apps including shell access, but not cron http://sourceforge.net/apps/trac/sourceforge/wiki/Cron%20service See overview at: http://sourceforge.net/apps/trac/sourceforge/wiki/WikiStart
Chinua: found an open source mailer on sourceforge called 'ServerMailer'. It is used by passing in mail server configuration, toAddress, fromAddress and message parameters through the command line.