I've set up a plan with a Perforce repository. It doesn't matter what I set the build schedule to be, if the build is enabled it is continuously polling the Perforce server for changes.
INFO | jvm 1 | 2007/03/29 11:41:41 | 2007-03-29 11:41:41,449 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command: INFO | jvm 1 | 2007/03/29 11:41:41 | C:\Perforce\p4.exe -u xxxxx -p xxxxx:1666 -c xxxxxx client -o INFO | jvm 1 | 2007/03/29 11:41:41 | 2007-03-29 11:41:41,449 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command: INFO | jvm 1 | 2007/03/29 11:41:41 | C:\Perforce\p4.exe -u xxxxx -p xxxxx:1666 -c xxxxx client -o INFO | jvm 1 | 2007/03/29 11:41:42 | 2007-03-29 11:41:42,561 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command: INFO | jvm 1 | 2007/03/29 11:41:42 | C:\Perforce\p4.exe -u xxxxx -p xxxxx:1666 -c xxxxx client -o INFO | jvm 1 | 2007/03/29 11:41:42 | 2007-03-29 11:41:42,561 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command: INFO | jvm 1 | 2007/03/29 11:41:42 | C:\Perforce\p4.exe -u xxxxx -p xxxxx:1666 -c xxxxx client -o
Our Perforce administrators will not allow this, so because of this I have to keep the plan disabled and only enable it to run a build manually which totally defeats the purpose.