The JetBrains Blog

Blog

  • Blogs by Topic
    • English
    • Deutsch
    • Français
    • 日本語
    • 한국어
    • Русский
    • Türkçe
    • IDEs

      • AppCode
      • CLion
      • DataGrip
      • DataSpell
      • Fleet
      • GoLand
      • IntelliJ IDEA
      • PhpStorm
      • PyCharm
      • Rider
      • RubyMine
      • WebStorm
    • Plugins & Services

      • Big Data Tools
      • Code With Me
      • Quality Assurance
      • JetBrains Platform
      • Rust
      • Scala
      • Toolbox App
      • Writerside
    • Team Tools

      • Datalore
      • Space
      • TeamCity
      • Upsource
      • YouTrack
      • Hub
      • Qodana
    • .NET & Visual Studio

      • .NET Tools
      • ReSharper C++
    • Languages & Frameworks

      • Kotlin
      • Ktor
      • MPS
    • Education & Research

      • Edu Products
      • Research
    • Company

      • Company Blog
      • Security
Teamcity logo

The TeamCity Blog

Powerful CI/CD for DevOps-centric teams

Follow
  • Follow TeamCity:
  • Twitter
  • Youtube
  • RSS
Get TeamCity
Follow
  • Follow TeamCity:
  • Twitter
  • Youtube
  • RSS
  • News
  • Releases
  • Features
  • Webinars
  • How-To's
  • Guest posts
Get TeamCity

agentless

Agentless build steps: API update and support in AWS CodeDeploy plugin

In version 2020.2, we introduced the concept of agentless build steps that can be run outside TeamCity, in third-party services. With this functionality, you can detach an agent from a build even before the build finishes. This helps manage agents more effectively: the earlier an agent gets free from one build, the sooner it can start another build. In the scope of the whole server, it allows running more builds on fewer agents. To learn more about agentless steps, watch this video. What tasks can be offloaded to a third party? Common examples are deploying software with services like Oc

Maria Kudryavtseva Maria Kudryavtseva

New in TeamCity 2020.2: Agentless Build Steps

TeamCity 2020.2 comes with an exciting new feature called “agentless build steps”. It is useful whenever you want to call an external service during your builds that does not respond immediately, but takes an indefinite amount of time to run. Examples could be 3rd party deployment services, scripts running on your servers to prepare environments, or services used for manual QA verifications and deployment approvals. Before TeamCity 2020.2, such calls would block your build agent while it was waiting for the response from the service. With “agentless build steps” you can now reuse the agent fo

Marco Behler Marco Behler
  • Privacy & Security
  • Terms of Use
  • Legal
  • Genuine tools
  • English
  • Deutsch
  • Français
  • 日本語
  • 한국어
  • Русский
  • Türkçe
Copyright © 2000–2022 JetBrains s.r.o.