To put it simple, using different types of plugins you make the UI handle the plugin updates differently.

You can specify BUNDLE_DEV_URL as a and use incrementally updated JavaScript file directly from the Webpack server.

By default, the Webpack Server starts on a port 8080. In this case, the Webpack Server starts in the Docker container.

To run a plugin using the Webpack Development server mode, use From there you can build a plugin and add it to the TeamCity instance. In this case, Docker container will generate a bundle.js and put it to the directory /demoPlugins-server/src/main/resources/buildServerResources. We recommend you to use the Docker image to build the frontend part. *All those steps also described in Main Plugin Guide Frontend Part (Controlled- and React-plugins): We are using TeamCity 10 installed on Windows in our setup.ĭownload and install a Java IDE we are using Intellij IDEA Community Edition, which has a built-in Maven integration.ĭownload and install Apache Maven. Since you are going to use this machine to test your plugin, it is recommended that this TeamCity server is of the same version as your production server. Java 1.8 is required, the 32-bit versionis recommended, the 64-bit version can be used.ĭownload and install TeamCity on your development machine. Set the JAVA_HOME environment variable on your system. To get started writing a plugin for TeamCity, set up the plugin development environment.ĭownload and install OpenJDK 8 (e.g. JetBrains / TeamCity UI Plugin Development Documentation.JetBrains / TeamCity Blog post about the UI Plugins.There are some useful resources for this repository: This repository describes the way to develop plugins.

Sakura plugin free download