By default, when created, all configurations are active and can be paused manually as described below or automatically if the project is archived.
#HOW TO PAUSE FORTE AGENT DOWNLOAD CODE#
Regular build configuration, defining actions and rules to apply to the source code all the settings above are applicableĭeployment build configuration, which deploys artifacts of other builds to some environmentĬomposite build configuration, which aggregates results from several other builds combined by snapshot dependencies and presents them in a single placeĪ build configuration is characterized by its state visible in the UI which can be paused or active. The following build configuration types exist in TeamCity: Triggers, which are rules defining when to start a new buildįailure conditions specifying when a build will be marked as failedįor snapshot dependencies, TeamCity will run all dependent builds on the sources taken at the moment the build they depend on startsįor artifact dependencies, before a build is started, all artifacts this build depends on will be downloaded and placed in their configured target locations and then will be used by the buildĪgent requirements specifying whether a build configuration can run on a particular build agent.īuild configuration settings and build behavior may vary depending on the type of build configuration. Version control settings, defining how the source code is retrieved from VCS, where it is checked out to, and so onīuild steps, that are sequentially run actions: for example, running msbuild, a script, or unit tests