keronmedi.blogg.se - Teamcity license

#TEAMCITY LICENSE INSTALL#
#TEAMCITY LICENSE MANUAL#
#TEAMCITY LICENSE PRO#

Register the environment variable named NDEPEND_TEAMCITY_HOME Once the TeamCity server is restarted you can check when creating a new Build Step, that the NDepend Build Step is available.

Or from a command console you can type net stop teamcity and then type net start teamcity.Ĭheck the plugin has been installed properly.

From a PowerShell console you can type Restart-Service TeamCity.

Once the plugin file is copied to the TeamCity plugin directory you need to restart the teamCity server.įor that you need to restart the associated Windows service.

To check this is the right plugin directory, you can check the environment variable named TEAMCITY_DATA_PATH value, that should refers to C:\ProgramData\JetBrains\TeamCity.

Typically this directory is C:\ProgramData\JetBrains\TeamCity\plugins.

Copy this file to the TeamCity plugin directory.

It can be found in $NDependInstallDir$\Integration\TeamCity.

The plugin file is named ndepend-teamcity.zip.

Step by step install: Copy/paste the plugin file to the TeamCity plugin folder Please watch this 5 minutes videos, or follow instructions below the video:

#TEAMCITY LICENSE INSTALL#

Let the TeamCity agent on this machine know where NDepend is installedīy registering the environment variable named NDEPEND_TEAMCITY_HOME with the NDepend install location,Īnd then restart the TeamCity build agent.

Copy/paste the plugin file to the TeamCity plugin folder, and then restart the TeamCity server.

#TEAMCITY LICENSE MANUAL#

Once you've installed NDepend somewhere on the machine that hosts TeamCity, there are two manual steps to install the NDepend Team City plugin. Hence if you want custom options values, you need to save these values in the VisualNDependOptions.xml file that corresponds to the Windows user used to run .įirst notice that the TeamCity agent that runs NDepend must be a Windows machine, but the TeamCity server can run on any OS. Notice that options like code query execution time-out are stored in the fileĬ:\Users\\AppData\Roaming\NDepend\VisualNDependOptions.xml which is available on a Windows user basis. Notice that the same Windows user must be used for activating thought VisualNDepend.exe, and for running the TeamCity NDepend plugin executable. If the machine is not connected to internet, a simple offline activation procedure will be proposed instead, and must be fulfilled in order to run the SonarQube NDepend plugin.

Or /RegLic XYZ to register a seat of the Build-Machine license with key XYZ. To do so, once NDepend files are unzipped on the machine, just run from a command window /RegEval to start evaluation To run the TeamCity NDepend plugin on a machine NDepend must be activated on it first.

#TEAMCITY LICENSE PRO#

A pro BuildMachine license seat is needed per machine that runs a TeamCity agent and that runs NDepend.Ī machine that runs the TeamCity server but doesn't run a TeamCity agent doesn't need a pro BuildMachine license seat.