First attempt to chaining the pop rollups when run from the global schedulable.
Run it or schedule it only if there are records left to process.
Breaking the opp rollup class into 4 different ones. Setting the global scheduler to run hourly. Each hour it will run the max number of batch processes that it can (under 5).
Fixing compilation error in test class.
Changing purge-on-delete to false.
Removing deleted class from package.xml.
Test ordering issue in Summer14. Also resolved in purgeOnDelete-false branch.
Fixing test to match changes.
Fixing test to match changes.
We were getting a compile error because we had changed the constructor. We may not need constructor with arguments.
I had renamed the class. Missed it.
Seems like the soft credit rollup is the same as the contact rollup?
The execute method from UTIL_IScheduled should return a boolean indicating whether the job was run or not (for batch jobs there is a limit of how many you can have executing + in the queue).
Running it only late at night, instead of every hour. Since we only have 6 jobs, and it can run up to 5 batch jobs at once, scheduling it 3 times would be more than enough (that makes 15).
I hadn't ported the changes properly from https://github.com/SalesforceFoundation/Cumulus/compare/feature/purgeOnDelete-false#diff-2cccd7bf48b7a9cc113ff564acd802a8R410.
Fixing compilation errors after refactoring.
Just adding log message.
Merge pull request #869 from SalesforceFoundation/feature/860-too-many-batch-jobs

Feature/860 too many batch jobs
Merge dev into feature/850-addr-verif-batch-test