This way, you can also update distribution files in a third-party storage, like Amazon S3. The benefits you get from TeamCity in this case are flexible automation, synchronization with the previous build stages, and a convenient view of build results in the TeamCity UI. Just add a build step, select any such runner, and enter commands as if in a regular terminal. This is the most straightforward approach. Via a command line, using any general runner like Command Line or PowerShell. Here's how you can deploy your build artifacts: We suggest that you always use deployment configurations to deliver your software to production. See more details about these and other features of such builds. Personal builds are disabled to prevent any accidental deployment. The Run button of such a build changes to Deploy.Īll dependency builds get an extra Deployments section of Build Results, from where you can quickly deploy the product. In addition to that, a deployment config offers several enhancements for an easier and transparent workflow: Unlike them, deployment builds work almost like regular ones: you can add the same steps and features or tweak the same settings. We talked about composite builds in the previous tutorial. When you create or edit a build configuration, you can change its type from Regular to Composite or Deployment. However, if your project is rather simple and you build it with a single configuration, you can deploy its result with just the final step of this configuration - it's totally up to you.ĭepending on your environment, all the deployment processes can be executed on a build agent or in any third-party system. Most often, a deployment build is a finishing stage of a pipeline, or build chain. This article gives an overview of the deployment instruments offered by TeamCity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |