Schedule builds for InsuranceSuite applications
For each InsuranceSuite application, you must create schedules separately.
Define schedule details
-
In the Automated Builds app, select + Create schedule.
-
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:
*.-
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
Dockerize Application is selected by default but isn't 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:
(Deprecated) Customize build parameters
The division of test suites to pre-merge and post-merge is deprecated. Now, you enter the names of suites and with the branch filters you determine on which branches they should be executed.
By default, scheduled builds use the parameter values configured in a TeamCity project for a selected application. You can customize this configuration for the following suites:
- Server tests
- Smoke tests
- Behavior tests
Customized parameters apply only to the scheduled builds. This step doesn't override the default configuration for your builds.
To customize build configuration:
-
Select Configure next to a build.
-
In the Pre/Post-merge test suites setup [deprecated] setup, enter test suite names.
Add each test suite in a new line.
-
Select Save.
During editing a schedule, you can still choose between the following setups:
- Pre/Post-merge test suites setup [deprecated]
- Test suites setup
Once you select the Test suites setup and save your changes, you can't go back to the Pre/Post-merge test suites setup [deprecated].
To delete a test suite, edit the schedule and remove the suite from the suite list.
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 the following suites:
- Server tests
- Smoke tests
- Behavior tests
Customized parameters apply only to the scheduled builds. This step doesn't override the default configuration for your builds.
To customize build configuration:
-
Select Configure next to a build.
-
Enter test suite names.
Add each test suite in a new line.
-
Select Save.
To delete a test suite, edit the schedule and remove the suite from the suite list.
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.