There isn't much to tell really. Most of it is set up through Hudson's (now Jenkins) UI.
I'll do my best to give a brief summary of what is needed, and to answer your questions:
1. There really aren't any "scripts" to speak off, there's one Groovy script I wrote to help copy build properties from the Jenkins UI to a build.properties file. That script is checked in to SVN under build-support/ci.
2. There are currently two hosting environments, the first is the machine that runs Jenkins, and the second is the hosting environment that hosts the final artifacts. The Jenkins machine is my Mac laptop, and the file host is my hosting environment for tellurianring.com
. Jenkins just uses FTP to upload the files to the server.
Jenkins provides an executable war file which runs an embedded Winstone server. I just use that, although it can easily be run Jetty, Tomcat, Glassfish, Resin, or any other J2EE Servlet Container.
Besides the regular requirements for building jEdit from source, I've installed wine (through macports) so that the windows installer can be built, and Groovy which I use as a scripting language to run the copy_properties.groovy script found in SVN. The windows installer requires that you have a utility installed, but instructions for that can be found in jEdit's own release documentation. All the other installers are built easy enough without having to install anything else (you may need to install x-code tools, but most developers will need to do that anyway), with the exception of the debian installer which can be built, but requires that Vampire sign it.
The largest part of setting up the environment is just creating and setting up the jobs in Jenkins itself. Unfortunately some build.properties require an absolute paths which means that each Jenkins Job does need to have some manual configuration.
Luckily Jenkins keeps all configuration in files that can easily be copied from one machine to another (as has been the case when I've upgraded machines). If someone would like the environment I could provide a tar.gz file with all the jobs and settings. All that would be required is it be dropped in there ~/.hudson directory and voila you have yourself a complete copy of the jEdit daily build environment.
Actually, is there anyone one here who would like to take over the daily-builds? You would need to get a new file host for the build artifacts since it's currently using my personal hosting environment, but I could help anyone who's interested to get their environment set up.
On Fri, Jun 15, 2012 at 1:17 AM, Jarek Czekalski <email@example.com>
I know you once told me something about the daily builds machine, but could you know collect the details together:
1. Are your scripts uploaded to jedit so that we could copy them and reproduce the machine?
2. What are hosting requirements to setup the environment? I mean is Tomcat, Glassfish or something like that necessary?
Learn from the past. Live in the present. Plan for the future.
jEdit <http://www.jedit.org> - Programmer's Text Editor
Bazaar <http://bazaar.canonical.com> - Version Control for Humans