Re: Building with Jenkins slaves
Re: Building with Jenkins slaves
- Subject: Re: Building with Jenkins slaves
- From: Paul Hoadley <email@hidden>
- Date: Fri, 02 Nov 2012 10:44:42 +1030
On 01/11/2012, at 10:03 PM, Paul Hoadley < email@hidden> wrote: We use a totally custom ant base build setup that uses ivy (plus a ruby script that turns the .classpath into a ivy dependency list). The custom build files are checked out from a remote git repo into the project, and ivy downloads the required build artifacts from jenkins using the jenkins_url.
Ah, thanks for that. Downloading it like that from the master hadn't occurred to me. I'll give it a shot.
For the record, that did work with the Amazon EC2 plug-in: I successfully got some jobs to build, spinning up t1.micro instances on demand. I'm shelving the idea for now, though, as it does seem to be held together by duct tape to some extent, and would need a bit of work to make me convinced it was robust.
Quinton—I don't suppose your custom scripts are shareable?
Dave—could you give a quick summary of what setupWonderProjectWorkspace.sh is doing starting here?
# Step through them to get the list of WO frameworks on their Classpath.
for PROJECT in $PROJECTS; do
I note that you suggest looking for other Jenkins jobs with matching names as a last resort—what's you preferred approach for a job getting the build products of another job then, such as one of your own frameworks on which the current job is dependent?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden