Re: Scheduled build always say build not required

On 3/28/06, Jim Hague <[email protected]> wrote:
> On Monday 27 March 2006 23:27, Eric Minick wrote:
> > Interesting. The problem we had seen earlier is that the SVN adapter had
> > been deciding it was time to build too frequently. I believe that was
> > addressed in the most recent build. The approach taken, roughly, is to
> > request a list of changes since the date of the most recent build. The
> > svn client will return too many results due to a subtelty in how it
> > handles revisions. The driver will then filter out any results that
> > appear to have been checked in before the previous build. If there are
> > any revisions remaining, the build will execute.
>
> The 'Right Way' to determine whether a build is required with Subversion would
> simply to be to look at the change number at the base of the repository - if
> it is bigger than the change number at the previous build, off we go.

What if you're managing multiple projects in the same repository?

Project A gets built Monday by Anthill
Project B has a bunch of commits performed throughout Monday.
Project A's developer is on vacation Monday, no commits happen.
Tuesday, Anthill check the revision at the base of the repository -
the "right way" would trigger a build of Project A because the
revision number changed, even though no code in Project A changed.