----- Original Message -----
> From: "Itamar Heim"<iheim(a)redhat.com>
> To: "Mike Burns"<mburns(a)redhat.com>
> Cc: "Eyal Edri"<eedri(a)redhat.com>, infra(a)ovirt.org
> Sent: Thursday, January 19, 2012 3:46:38 PM
> Subject: Re: Jenkins Continuous Integration Server for oVirt is up and running!
>
> On 01/19/2012 02:13 PM, Mike Burns wrote:
>> On Thu, 2012-01-19 at 05:07 -0500, Eyal Edri wrote:
>>> fyi,
>>>
>>> oVirt project now has a Jenkins CI server[1] on
>>>
http://jenkins.ovirt.org.
>>>
>>> The CI server runs various jobs on oVirt components *[2] such as
>>> ovirt-engine,ovirt-node,etc..
>>> Every commit to
gerrit.ovirt.org will trigger the job
>>> 'ovirt_engine' which will run 'maven' build and verify that
the
>>> commit didn't break the code.
>>> If the commit did break the code, it will send an alert email to
>>> "engine-patches.ovirt.org" and to the commiter with a link to a
>>> log console containing the error.
>>> On success, the job will trigger other jobs such as "find_bugs",
>>> "gwt profiles", "create db", "unit-tests", each
testing a
>>> different part of the code.
>>>
>>> In time, more and more jobs will be added to jenkins, which will
>>> allow us to catch bugs much faster than before, and to improve
>>> code quality even more.
>>> If you have questions, don't hesitate to ask me or
>>> infra(a)ovirt.org.
>>>
>>> [1]
http://jenkins-ci.org/
>>> [2] currently only ovirt-engine is configured and working.
>>>
>>
>> Awesome, thanks for putting this together.
>>
>> I'm looking at ovirt-node now (and have already added part of the
>> config). Is there any plan to add a Fedora slave? ovirt-node as
>> it
>
> well, anyone can contribute machines for their favorite/needed distro
> and ask eyal to add them as slaves with relevant labels so jobs will
> run
> on them.
> I think eyal can also configure to run a job multiple times on
> different
> slaves (multi config job), to check node/vdsm don't break on any
> distro
> which added a slave.
>
> I'll add a fedora machine and send Eyal the details to add as a
> slave.
> before i do that, I want eyal to take a look at the jenkins EC2
> plugin,
> so we can see if we can have the guest only up when needed.
>
I installed the EC2 plugin, need some info on the cloud.
attached is the configuration screen ( under
http://jenkins.ovirt.org/configure )
can the plugin start/stop existing slaves, or creates them as needed?
does amazon support a delegated user to an account with limited set of
permission to only start/stop existing slaves based on permissions?