This topic gives an overview of the options for editing a project configuration file.
Each project is controlled by a project file that defines the configuration details for the project. You can edit the configuration file to:
- change the display name for the project across all client applications - see Changing the project name
- define a new build or checkout location for snapshots - see Changing the build or checkout locations
- edit the checkout commands to reflect changes to your source code repository - see Defining checkout commands manually
- edit the build commands to reflect changes to your build methods - see Defining build commands
- updating the build commands to work with an incremental build system - see Configuring a project to use incremental builds
- define how often new snapshots of the code are analyzed - see below.
Editing the project file
You can edit the project file using your preferred text editor.
Changes to most elements in the project file are applied to all new snapshots created after the change (created using the addSnapshot or addLatestSnapshot command). If you define a new display name for the project, then this change is seen on all dashboards built after the change (built using the buildDashboard command).
Changing the minimum period between new snapshots
The frequency at which new snapshots are created depends on:
- Frequency at which the addLatestSnapshot command is called by the data processing script (see Scheduling data processing).
days-between-updateselement in the
When the addLatestSnapshot command is called, the date of the most recent snapshot and the value of the
days-between-updates element are checked. A new snapshot is added to the project only if the number of days since the most recent snapshot matches or exceeds the value of the
When addLatestSnapshot is called it will no longer run if a snapshot for yesterday is already available unless the
--overwrite flag is specified.