Agent-side Object Model

Added by Pavel Sher, last edited by Yegor Yarko on Jan 16, 2009  (view change)
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search
Searching TeamCity 4.x Documentation
Table of Contents

On the agent side agent is represented by jetbrains.buildServer.agent.BuildAgent interface. BuildAgent is available as a Spring bean and can be obtained by autowiring.

Build agent configuration can be read from the jetbrains.buildServer.agent.BuildAgentConfiguration, it can be obtained from the BuildAgent#getConfiguration() method.

Agent side events

There is jetbrains.buildServer.agent.AgentLifeCycleListener interface and corresponding adapter class jetbrains.buildServer.agent.AgentLifeCycleAdapter which can be used to receive notifications about agent side events, like starting of the build, build finishing and so on. Your listener must be registered in the jetbrains.buildServer.util.EventDispatcher. This service is also defined in the Spring context.

Build

Each build on the agent is represented by jetbrains.buildServer.agent.AgentRunningBuild interface. You can obtain instance of AgentRunningBuild be listening for buildStarted(AgentRunningBuild) event in AgentLifeCycleListener.

Logging to build log

Messages to build log can be sent only when a build is running. Internally agent sends messages to server by packing them into the jetbrains.buildServer.messages.BuildMessage1 structures. However instead of creating BuildMessage1 structures it is better and easier to use corresponding methods in jetbrains.buildServer.agent.BuildProgressLogger which can be obtained from the AgentRunningBuild.

If you want to construct your own messages you can use static methods of jetbrains.buildServer.messages.DefaultMessagesInfo class for that.

Labels

 
(None)