Label: plugin+agent

All content with label plugin+agent.
Related Labels: change , idea , delayed , run , paper , statistics , struts2 , admin , disabled , build , visual , openapi , grid , rspec , authentication , vcs , graph , environment , number , project , clean , authorized , hang , server , implicit , professional , teamcity , task , metric , home , disconnected , gem , tool , connected , deployment , system , sticky , https , packaging , label , ant , custom , date , connect , status , edition , policy , code , notifier , enabled , enterprise , eap , tray , ui , search , comment , key , result , committer , compatible , unauthorized , post , process , trigger , dump , commit , directory , open , studio , extend , property , draft , manage , vs , assign , license , web , test , evaluation , iblogextension , disconnect , configure , runner , personal , backup , troubleshooting , commercial , log , eclipse , tab , thread , reference , global , setting , chart , properties , variable , install , requirement , file , remove , configuration , rake , predefined , working , extending , ruby , upgrade , coverage , user more » ( - plugin , - agent )

Agent Side Extensions (TeamCity 3.x Documentation) AgentSide Extensions Currently, there are two ways to extend build agent: # Write a custom build runner # Write an extension to AntRunner (for instance, to process custom tasks) Both approaches use similar way of plugin packaging and deployment (see below ...

Agent-Side Extensions (TeamCity 4.x Documentation) Currently, there are two ways to extend a Build Agent: Write a custom build runner Write an extension to Ant Runner (for instance, to process custom tasks) In this section: Plugin Descriptor Spring container is used on the agent and server side. An example ...