We just explored how to configure Jenkins to run our test suite when we commit the code changes. Jenkins can also be configured to invoke our test suite at scheduled intervals. This is very useful, because we can gear it to make scheduled releases. Daily or weekly releases can provide potential customers with a nice cadence of release.
CI releases are usually understood to not necessarily be final, but instead provide bleeding edge support in case new features need to be investigated early and integrated by the customer.
The following steps are used to set up Jenkins as well as a copy of our tests, so we can poll it at a scheduled interval: