Schedule builds for InsuranceSuite applications

For each InsuranceSuite application, you must create schedules separately.

Define schedule details

1. In the Automated Builds app, select + Create schedule.

2. Provide the following details:

   • Name

     Schedule name must be unique within application.

     This field is case sensitive.

   • Branch filter

     Specify branches on which the selected builds will run.

     Add each rule in a new line. Branch names are case-sensitive. You can also use a wildcard: *.

     Examples

     • Include a specific branch:

       +:branch_name

     • Exclude a specific branch:

       -:branch_name

     • Include only the default branch:

       +:<default>

     • Include all branches:

       +:*

     • Include all branches except for the default one:

       +:*
       -:<default>

     • Include all branches prefixed with feature-:

       +:feature-*

   • Application

     Select an application for which you want to schedule builds: BillingCenter, ClaimCenter, PolicyCenter, or Contact Manager.

Select and configure builds

For InsuranceSuite applications, you can include the following builds in a schedule:

• Server tests
• Smoke tests
• Behavior tests
• API tests
• Dockerize application

Note:

Dockerize Application is selected by default but not required.

Build dependencies still apply when you create schedules. For example, Dockerize Application might automatically trigger Server Tests. Creating a schedule with only Dockerize Application means that both builds might run.

To select a build and add it to the schedule, use the check boxes:

Customize build parameters

By default, scheduled builds use the parameter values configured in a TeamCity project for a selected application. You can customize this configuration for server tests, smoke tests, and behavior tests.

Note:

Customized parameters apply only to the scheduled builds. This step does not override the default configuration for your builds.

To customize build configuration, select Configure next to a build.

To add a test suite to a build:

1. Select + Add.
2. Enter a test suite name.
3. Define whether to run the test suite as pre-merge, post-merge, or both.
4. Select Add.

To modify the values of Pre-merge and Post-merge for an already added test suite, use toggles.

To delete a test suite, hover over its name and select Delete.

Define date and time

To specify when to run the schedule, use cron syntax.

You can use the following values in a cron expression:

Field	Possible values	Special characters	Notes
Seconds	0–59	, - * /
Minutes	0–59	, - * /
Hours	0–23	, - * /
Day of the month	1–31	, - * / ? L W
Month	1–12 or JAN–DEC	, - * /
Day of the week	1–7 or SUN-SAT	, - * / ? L W	The first day of the week is Sunday.
Year	1970-2099 or empty	, - * /	This field is optional.

For example, you can set your schedule to run:

• Every Monday at noon: 0 0 12 ? * 2
• Every day at 6 p.m.: 0 0 18 1/1 * ?
• On the first Friday of every month at 8:15 a.m.: 0 15 8 ? 1/1 6#1

A cron expression is relative to the selected time zone. You can choose a different time zone from the drop-down list.

Additional settings

In this step, you can also define additional settings:

• Run only if there are pending changes

  By default, the builds run according to the schedule even if there are no changes in your code. To trigger builds only if there are pending changes, check this option.

• Active

  By default, your schedule is set to Active.

  You can also create inactive schedules and activate them later. For details, see Edit a schedule.