A random 'sessions id', which changes every time the TeamCity server is restarted.Whether the result of the fallback returned the same, better or worse information.When the DeploymentProvider needs to fallback to using the /api/Deployments endpoint when the /api/progessionĮndpoint does not return enough information.Exceptions (The top level exception message (without the stack tracce) with IP address and urls masked).Only basic feature usage information is tracked, with no personally identifiable information shared.Īny exceptions are masked to remove sensitive data. This information is used only to understand real world usage and guide future improvements.
This project uses Google Analytics to track feature usage and exceptions. You to track and monitor internal stats such as cache hits & misses, outbound calls, bresponse time and more. Metrics are exposed as a json endpoint at allowing
#TEAMCITY OCTOPUS UPDATE#
If you want to disable update checking, you can set the .check.enabled internal On the trigger dialog suggestion an upgrade. If you want to turn on logging, add the following to \conf\teamcity-server-log4j.xml:Ī check is made once every 24 hours to see if there is a new version available, and if so, shows a banner add mutation testing using something like Jester.Once a build is triggered, parameters will be passed to the build: Once the plugin is installed, add one of the triggers to your build. See TeamCity documentation for more info. Installationĭownload the latest release, and drop it into your /plugins folder. It is highly recommended that you use subscriptions where possible rather than this plugin, as this plugin adds reasonable load to your Octopus server due to the way it calls the API. This plugin was written before Octopus Subscriptions became available.
0 kommentar(er)
