[Anthill-pro] When builds are not forced, new builds are not made

[Eric Minick]

Yeah, a support ticket might be appropriate. The next thing to look at 
though would be to go to Search -> Requests and look for requests for 
this project from the time of the schedule firing. By drilling in the 
request, you should be able to see what, if anything, it's doing and 
find a log that indicates why Anthill decided to perform a build or not.

-- Eric

Evora, Hermes wrote:
> Hi Eric,
>
> Thanks for the reply.
> I do have selected the Quiet Period Type to "Change Log Quiet - Period Periodically polls the repository",  No on "Should Cleanup", and Any Agent on the "Agent Filter". However, I still only have builds if forced.
> Any other clue? Should I open a support ticket with Urbancode support?
>
> Thanks,
>
> Hermes Evora
>
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric Minick
> Sent: Thursday, July 02, 2009 6:19 AM
> To: AnthillPro user list.
> Subject: Re: [Anthill-pro] When builds are not forced, new builds are not made
>
> Hermes,
>
> You'll need to make sure the your project is configured to use a change 
> log style quiet period / changes check. You can verify that under 
> administration > Your Project > Quiet Period tab.
>
> -- Eric
>
> Evora, Hermes wrote:
>   
>> Hi all,
>>
>> It appears that all our scheduled triggers only work when forced to 
>> run a build. When builds are not forced, new builds are not made even 
>> if I check in new code.
>>
>> I just realized that all our scheduled triggers are set to force 
>> builds. We want to start building dependencies only when changed, so 
>> we need to uncheck the force build option. Doing that, builds won't start.
>>
>> From AH3 documentation I quote:
>>
>>
>>     "Scheduled Triggers
>>
>> Add a Scheduled Trigger to workflows in a similar manner to the 
>> Repository Trigger. Each Schedule Trigger runs on its own timer that 
>> polls the SCM for changes. If changes are detected, the build is 
>> registered with the schedule and kicked off when the schedule fires.
>>
>> Scheduled Triggers give the option to force a build regardless of 
>> whether source changes have occurred. Unless the forced option is set, 
>> AnthillPro will not initiate a build if no source changes are detected.
>>
>> "
>>
>> However, when we uncheck the force build, AH3 is failing to poll our 
>> Perforce SCM for changes, and the builds won't happen even if changes 
>> occurred.
>>
>> Questions: Is there any setting that we are missing? Is this a bug on 
>> AH3? Does this happens only when using Perforce?
>>
>> Thanks in advance for any input on this.
>>
>> Regards,
>>
>> *http://www.edmunds.com/etc/medialib/Images/media/static_pages/about.Par.75132.123.35.ImageRef.gif***
>>
>> *Hermes Evora | Senior Release Management Engineer***
>>
>> *Edmunds, Inc.***
>>
>> *1620 26th Street, Suite 400 South | Santa Monica, CA 90404***
>>
>> *hevora at edmunds.com <mailto:jfelczak at edmunds.com> | Desk-310-309-6419 
>> | M-310-353-6121***
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>