The ScheduleExecuterThrottle value on the Advanced/Internal Settings page found under Admin determines how often this polling occurs (it also controls the polling for whether it's time to do a scheduled build). The field specifies polling frequency in minutes.

I would suggest just disabling your build schedules during the outage period. Maybe at 12:45AM through 1:15AM (or whatever). This can be done through the API methods (BuildSchedules_GetSchedules and BuildSchedules_CreateOrUpdateSCMTriggered), or through a simple SQL Query (UPDATE BuildSchedules SET Active_Indicator = 'N'). We don't have a generic task scheduler built-in to BuildMaster, so you'd want to use Windows Task scheduler to run the enable/disables.

Yes, but not easily. Automatic build records (schedule, SCM-triggered, or URL-triggered) are not "soft deleted", so you must go to the audit logs and search for the "BSHDEL" event. This can be done from the UI or directly from the database with SELECT * FROM EventOccurences WHERE Event_Code='BSHDEL'

Yes; just set up an Source Control Triggered Automatic Build ( http://inedo.com/support/documentation/buildmaster/core-concepts/builds/source-control-triggered-builds ) that watches the desired path(s), and a build will be kicked off when that changes.

There may be a number of reasons why a builds aren't being created: Verify that there are releases for the target applications; a build cannot be created unless a release exists. Make sure the build schedule (under each app) is there, and not set to "disabled." Verify that the service is running. (Admin -> Service) Look for entries in the error log (Admin -> Errors) to see if anything popped up overnight. Verify that the ScheduleExecuterThrottle (Admin -> Advanced Settings) is a positive integer (default is 1).

The password being displayed is by design, since the same privilege (Builds_ManageBuildSchedules) is required to both view and edit the build schedules, therefore showing it on one page is essentially the same as showing it on the other. You can disallow users to view the schedule details by denying the Builds_ManageBuildSchedules privilege to whomever you do not want to view the passwords.

Thanks but I've had to revert back to 2.6.3 for now after spending most of the day trying to get the update to work. Will try again with 3.1 when it's available.