Build Keeps Triggering

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Build Keeps Triggering

Qazwart-2
I have a Subversion project which has some externals attached to it.
For some reason, the project keeps rebuilding over and over again. The
log simply says:

Aug 5, 2008 6:01:24 PM hudson.triggers.SCMTrigger$Runner run
INFO: SCM changes detected in ADINV-2.1.1. Triggering  #170

Over and over again. The build keeps happening every eight minutes.
The change log shows no changes.

The revisions shown on each build page are:

http://subversion/dev/modules/domain/trunk/repos/instance/bin : 6703
http://subversion.solbright.com/dev/modules/base/trunk/lib-har : 14868
http://subversion.solbright.com/dev/modules/dbutil/trunk : 12780
http://subversion.solbright.com/dev/modules/base/trunk/repos/lib : 14874
http://subversion.solbright.com/dev/modules/base/trunk/lib : 14868
http://subversion.solbright.com/dev/modules/base/trunk/repos/db/foundation : -1
http://subversion.solbright.com/dev/modules/base/trunk/repos/db/domain : 14866
http://subversion.solbright.com/dev/modules/adinventory/trunk : 14887
http://subversion/dev/modules/domain/trunk/repos/instance/conf : 12845
No changes.

Over and over again.

Is there anyway I can find out exactly what is triggering the build?
Is there a reason why one is at a "-1" revision? And, is that causing
the build trigger?

--
David Weintraub
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Build Keeps Triggering

Qazwart-2
Okay, it looks like there were some dead areas that couldn't be
updated. I went into the workspace, did a "svn status", and removed
all non Subversion directories. I then did a "svn update". A new build
fixed the issue of the "-1" repository number. It also reported on
about five sets of changes that were not included in previous builds.

It's been about 30 minutes since the last build, so I think the issue is solved.

Maybe I should not have the "svn update" box checked? That would make
Hudson clean out the directory and use "svn co" instead. Right? That
will increase the build times, but the build takes only 38 seconds,
and the checkout probably takes two or three minutes.

--
David Weintraub
[hidden email]



On Wed, Aug 6, 2008 at 12:24 AM, David Weintraub <[hidden email]> wrote:

> I have a Subversion project which has some externals attached to it.
> For some reason, the project keeps rebuilding over and over again. The
> log simply says:
>
> Aug 5, 2008 6:01:24 PM hudson.triggers.SCMTrigger$Runner run
> INFO: SCM changes detected in ADINV-2.1.1. Triggering  #170
>
> Over and over again. The build keeps happening every eight minutes.
> The change log shows no changes.
>
> The revisions shown on each build page are:
>
> http://subversion/dev/modules/domain/trunk/repos/instance/bin : 6703
> http://subversion.solbright.com/dev/modules/base/trunk/lib-har : 14868
> http://subversion.solbright.com/dev/modules/dbutil/trunk : 12780
> http://subversion.solbright.com/dev/modules/base/trunk/repos/lib : 14874
> http://subversion.solbright.com/dev/modules/base/trunk/lib : 14868
> http://subversion.solbright.com/dev/modules/base/trunk/repos/db/foundation : -1
> http://subversion.solbright.com/dev/modules/base/trunk/repos/db/domain : 14866
> http://subversion.solbright.com/dev/modules/adinventory/trunk : 14887
> http://subversion/dev/modules/domain/trunk/repos/instance/conf : 12845
> No changes.
>
> Over and over again.
>
> Is there anyway I can find out exactly what is triggering the build?
> Is there a reason why one is at a "-1" revision? And, is that causing
> the build trigger?
>
> --
> David Weintraub
> [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]