[Anthill-pro] Anthill wants to know if a build is required, butI don't want it to care

[Eric Minick]

That could be it. I would check the command line command generated by 
Anthill and try that manually. There might be flag choices there that 
are important. If I recall correctly, we are asking for extra tag 
information so we can more easily see what changes happened on a 
different branch. That results in a pretty verbose log. You might also 
check the contents of the revision log generated by that command (in the 
cvs log in the intranent) and see if it seems to be filled with those tags.

-- Eric

Bryan Dotzour wrote:

>Eric: 
>
>Thanks for the response and your suggestion seems attractive and doesn't
>sound too bad.  I guess you're right, however, in that it is really nice
>to have that revisions log in the email.  Allow me to give you a little
>more information and ask you another question about how Anthill is
>finding revisions.
>
>For a time I had misconfigured our build to be tagging files in CVS each
>time it built .. every hour!  This happened with two branches for about
>a week so there are lots and lots of tags on all of our files.  Would
>this cause the revision detection to be slower?  It takes less than a
>minute to get the log information from CVS (I manually tested the batch
>file that Anthill generates) so I assume the rest of that time must be
>in Anthill.
>
>Do you think if I went through and removed all those unwanted tags that
>it would speed up the revision detection process at all?
>
>-----Original Message-----
>From: anthill-pro-bounces at lists.urbancode.com
>[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
>Minick
>Sent: Monday, August 28, 2006 2:33 PM
>To: anthill-pro at lists.urbancode.com
>Subject: Re: [Anthill-pro] Anthill wants to know if a build is required,
>butI don't want it to care
>
>Bryan,
>
>What you've communicated to Anthill with the force build flag is that 
>you don't want to make the build or don't build decision based on the 
>presence of revisions. The assumption made is that you still want the 
>revision log which has some intrinsic value.
>
>Evidently that's a poor assumption in your case. One outstanding task 
>for us is to give you the option to get the revision history using the 
>CVS history command which would be much faster but isn't supported by 
>all versions of CVS. If it was fast, maybe you'd find a revision log 
>more attractive.
>
>In the meantime, I think the goal would be to give you an automated way 
>of using the "Do not check for revisions" flag might be effective for 
>that build track. I think a Build Event Action triggered on the build 
>request might do the trick.
>
>You might try a script that like:
>
>// Fetch Properties from the script wrapper.
>buildDef = scriptWrapper.getProperty("buildDefinition");
>
>// Never check for revisions
>buildManager = buildDef.getBuildOwner().getBuildManager();
>buildManager.setNotCheckingRevisions(buildDef, isNotCheckingRevisions);
>
>
>Or you could get fancy and try to limit this behavior to scheduled 
>builds, or forced builds.
>
>// Fetch Properties from the script wrapper.
>buildDef = scriptWrapper.getProperty("buildDefinition");
>
>// Never check for revisions
>if (buildDef.getUserName().startsWith("SCHEDULE") &&
>buildDef.getForcedBuildFlag()) {
>  buildManager = buildDef.getBuildOwner().getBuildManager();
>  buildManager.setNotCheckingRevisions(buildDef,
>isNotCheckingRevisions);
>}
>
>
>Regards,
>Eric
>
>
>
>
>Bryan Dotzour wrote:
>
>  
>
>>I'm using Anthill 2.6.1 and I'm trying to troubleshoot an issue where 
>>our build takes way longer than you'd think it should. I can provide 
>>more information if desired, but basically it turns out that my build 
>>gets broken down into the following tasks:
>>
>>1. Clean up (takes almost no time)
>>
>>2. Checkout (takes just under 4 minutes)
>>
>>3. Is Build Required (takes almost 12 minutes!!!)
>>
>>4. All my hourly build tasks including DB construction, unit tests, 
>>etc (takes about 12 minutes)
>>
>>The thing I don't understand is the "Is Build Required" step. From 
>>what I can see, it looks like it's getting the CVS log for every file 
>>in the project since the last time the build was run. Presumably it's 
>>doing this to find out if any revisions have been made and thus it can
>>    
>>
>
>  
>
>>decide whether or not a build is required. My issue with this is that 
>>I have my build set up to delete all the files from the disk after the
>>    
>>
>
>  
>
>>build is run. I also set my schedule up to "Force builds". In my mind 
>>this means I want the build to occur no matter if anything in CVS 
>>changed at all. I don't understand then why I'm waiting 12 minutes to 
>>check revisions when I clearly don't care if there are any revisions. 
>>How can I tell Anthill that it shouldn't care either?
>>
>>I'm confused and wondering if I've got my build set up strangely or if
>>    
>>
>
>  
>
>>I'm completely missing a core concept here. Any help or comments would
>>    
>>
>
>  
>
>>be greatly appreciated.
>>
>>Thank you,
>>
>>Bryan
>>
>>-----------------------------------------------------------------------
>>    
>>
>-
>  
>
>>_______________________________________________
>>Anthill-pro mailing list
>>Anthill-pro at lists.urbancode.com
>>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>> 
>>
>>    
>>
>
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
>