Hello, For all those using Jenkins as a build server—is anyone running slaves? I've just spent some time experimenting with the Amazon EC2 plugin, with a view to having our always-on Jenkins CI instance supplemented by a swarm of t1.micros when the build queue got out of hand.
But regardless of the setting (that is, I don't think I hit a problem peculiar to EC2), are the scripts we're all using on Jenkins amenable to building on slaves? (Our scripts have diverged a bit from the original ones published, and the ones maintained by Dave Avendasora, but they're quite similar in principle.) In particular, it strikes me that needing access to the build products of upstream jobs is going to be a show-stopper, isn't it? From what I can tell, when a job is farmed out to a slave, all it gets is that job—there's no access to the build products of other jobs. So this breaks the kind of thing that, say, Dave's script: https://github.com/avendasora/WOJenkins/blob/master/Build/WonderProjects/WorkspaceSetupScripts/setupWonderProjectWorkspace.sh does starting at line 155, linking to other build products (though I note that script does that only as a last resort). Our scripts seem to be more directly descended from Mike Schrag's original stuff. So anyway, is anyone building WebObjects jobs using a master-slave setup? (Dave, do your scripts handle this?) Otherwise, looks like I'm going to have to scale up rather than out as I had hoped. -- Paul Hoadley http://logicsquad.net/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
