#Teamcity builds how to#
#Teamcity builds download#

We can configure a dedicated VCS trigger for each and every build configuration in the chain. In the configuration dialog, we have to enable вЂњTrigger a build on changes in snapshot dependenciesвЂќ checkbox. This is because itвЂ™s possible to tell the trigger to monitor for the changes in the dependencies. In our example, there are two build configurations but we will only need one VCS trigger. The VCS trigger is the one that reacts to the changes in a version control system. There are various kinds of triggers that are possible to set up for a build configuration in TeamCity. The result is visible on the Build Chains tab of the project: Consequently, all the dependent build configurations that form a build chain via the snapshot dependencies will be added to a build queue. When the TodoImage build configuration is triggered, TeamCity makes sure all the dependencies for this build configuration are up to date. For our current example, the default configuration is sufficient. You can read about the various settings in the documentation. There are a number of settings associated with the snapshot dependency. In the dialog, locate the build configuration it will depend on and click Save. To configure a snapshot dependency, go to the Dependencies tab in the build configuration settings and click the вЂњAdd new snapshot dependencyвЂќ button.

#Teamcity builds how to#

The documentation page describes how to configure the artifact rules in more detail. In the dialog, locate the build configuration from which the files should be downloaded and specify the patterns to match the file path(s). On the Dependencies tab, click the вЂњAdd new artifact dependencyвЂќ button.

#Teamcity builds download#

Any other build configuration can download the file by configuring the corresponding artifact dependency. The TodoApp build configuration publishes an artifact to the todo.jar file. There are two kinds of dependencies that we will need to configure: the snapshot dependency and the artifact dependency. The second build configuration, TodoImage, depends on the TodoApp build configuration and builds a Docker image. First, we will build the application, and then build the Docker image with the binary produced in the first step.ДЇirst the build configuration, TodoApp, builds the Spring Boot application and publishes an artifact as a result. We are going to build this project in two steps. In addition, there is a Dockerfile for building a Docker image. The repository includes a Gradle project that builds a Spring Boot application. To create a simple build chain, it is enough to create two build configurations and configure a snapshot dependency from one configuration to another.ДЇor this example, we are using a GitHub repository. In this blog post, we will explain how to create a build chain in TeamCity by configuring the snapshot dependencies for the build configurations. But most of all, it makes the overall maintenance significantly easier. The way TeamCity works with build chains enables quite a few interesting features, including parallel execution of the builds, re-using the build results, and synchronization for multiple source control repositories. We can split the steps into multiple build configurations and use TeamCity snapshot dependencies to link the configurations into a build chain. However, if the number of steps grows too large, it makes sense to examine what the build configuration is doing вЂ“ maybe it does too many things! You can define as many build steps as you like in one build configuration. A build configuration consists of the build steps and is executed in one run on the build agent. In TeamCity, when we need to build something, we create a build configuration.