Development Environment

Added by Yegor Yarko, last edited by Ekaterina Ivanova on May 18, 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

Plugin Reloading

If you make changes to a plugin, you will generally need to shut down the server, update the plugin, and start the server again.

The following hints can help you eliminate the restart in the certain cases:

  • if you do not change code affecting plugin initialization and change only body of the methods, you can attach to the server process with a debugger and hot-swap the code.
  • only for plugins installed as separate folder: if you make a change in some resource (jsp, js, images) you can copy the resources to webapps/ROOT/plugins/<plugin-name> directory to allow Tomcat to reload them.
    Setting JspServlet development mode to true in tomcat/conf/web.xml can speedup Tomcat reloading logic.
  • only for plugins installed as separate folder: change in build agent part of plugin will initiate build agents upgrade

If you change TeamCity core JavaScript or CSS, you will also need to pass "-DTC.res.disableCache=true" JVM option to TeamCity server to disable JS and CSS resources merging/caching.



See Also:

Labels

 
(None)