So if you ask yourself, what to do to improve your build runner, the answer is simple. So, in most cases one will not need to cache those instances in a plugin code.

We’ve added runnerFinished event and updated almost all build-related events signatures to contain AgentRunningBuild and BuildRunnerContext instances. AgentLifeCycleListener interface now provides BuildRunnerContext in build step related methods. Note that there is no getter for BuildRunnerContext in AgentRunningBuild. Starting with TeamCity 6.0 AgentRunningBuild will only describe a build. We’ve introduced new interface BuildRunnerContext that provides parameters for build runner. I hope this post will help you to painlessly improve your build runner plugins.ĪgentRunningBuild interface no longer represents parameters for a build runner. So today, I’m going to shed some light on the major agent-side API changes that we’ve made to support multiple build steps.

NET build runners, I believe that plugin developers might have some questions to be clarified. After our posts about TeamCity’s new multiple build steps (previously called “ multiple build runners“) feature and further changes in.

Download teamcity octopus