EC2 plugin not compatible with git plugin?

[David Kennedy]

I've been trying to use the EC2 plugin to farm out builds to, eg, 32
bit machines, 64 bit machines, etc, and while I've had some challenges
with nodes starting, I've got something working. I've a master machine
which doesn't do builds, just scheduling and reporting, and I want EC2
instances to do all builds depending on how the job is tagged (eg,
"linux && 64bit").

However, this morning, I see a few dozen builds during a period where
no-one was checking in. Each build is identical to the one before, no
changes, but each says it was triggered by an SCM change?!

I poll the SCM (github) every few minutes to check for changes. The
polling log for each build says

Started on Mar 3, 2011 6:16:51 AM
Workspace is offline.
Scheduling a new build to get a workspace.
Done. Took 0 ms
Changes found

Well, the workspace won't exist, as this is on the master (I think)
which doesn't build, and the remote EC2 machine might actually be
shutdown by now (depending on demand).

I found this posts whichs explain that if the workspace isn't there to
compare to, the Git plugin fires off a build:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/4b96aad9722c8074/a1b2f293f4c1fbc0?hl=en&lnk=gst&q=git+spurious#a1b2f293f4c1fbc0

So... if I'm using the EC2 plugin it looks like the Git plugin can't
find changes for me. I'm not sure how to address this, any ideas?

Dave

(All above with Jenkins 1.399, freshly installed two days ago)

[David Kennedy]

I think this is related to at least this bug:
http://issues.jenkins-ci.org/browse/JENKINS-7643

...but for now, and in case anyone else is having a similar issue,
we've avoided the problem
by switching polling to using this
http://wiki.hudson-ci.org/display/HUDSON/URL+Change+Trigger
to pick up the authenticated RSS feed from our GitHub repo. It's also
an option to use a
GitHub service hook to call into Jenkins, but as we're (many
builds)<--->(one repo) for now,
the RSS trigger is simpler.

On Mar 3, 11:00 am, David Kennedy <dkenn...@cloudopt.com> wrote:
> I've been trying to use the EC2 plugin to farm out builds to, eg, 32
> bit machines, 64 bit machines, etc, and while I've had some challenges
> with nodes starting, I've got something working. I've a master machine
> which doesn't do builds, just scheduling and reporting, and I want EC2
> instances to do all builds depending on how the job is tagged (eg,
> "linux && 64bit").
>
> However, this morning, I see a few dozen builds during a period where
> no-one was checking in. Each build is identical to the one before, no
> changes, but each says it was triggered by an SCM change?!
>
> I poll the SCM (github) every few minutes to check for changes. The
> polling log for each build says
>
> Started on Mar 3, 2011 6:16:51 AM
> Workspace is offline.
> Scheduling a new build to get a workspace.
> Done. Took 0 ms
> Changes found
>
> Well, the workspace won't exist, as this is on the master (I think)
> which doesn't build, and the remote EC2 machine might actually be
> shutdown by now (depending on demand).
>
> I found this posts whichs explain that if the workspace isn't there to

> compare to, the Git plugin fires off a build:http://groups.google.com/group/jenkinsci-users/browse_thread/thread/4...