anchor.diff:  * `agentOptions` : Options passed to the TeamCity agent via the `TEAMCITY_AGENT_OPTS` environment variable.
   * `plugins` : The collection of plugins to be deployed to the TeamCity server for this environment. Defaults to the
   plugin output by the `serverPlugin` task when the `com.github.rodm.teamcity-server` plugin is also applied.
  +
  +The following Gradle properties can be used to override the properties for a specific environment from
  +the command line or by setting a value in a gradle.properties file. Replace `<environment>` with the name
  +defined in the build script.
  +
  +* `teamcity.environments._<environment>_.downloadUrl`
  +* `teamcity.environments._<environment>_.homeDir`
  +* `teamcity.environments._<environment>_.dataDir`
  +* `teamcity.environments._<environment>_.javaHome`
   
   ==== Tasks
   
  
positive.code: The `publishPlugin` task requires a {uri-jetbrains-hub-token}[JetBrains Hub token] to publish a plugin to the
  repository as shown in the following examples.
  
  The following example configures the publish task.
  
  [source,groovy]
  [subs="attributes"]
  
negative.code: 
  The plugin archive published to the {uri-gradle-plugin-portal}[Gradle Plugin Portal] contains four plugins:
  
  * `com.github.rodm.teamcity-server` - Provides tasks to package, sign and publish a TeamCity plugin.
  * `com.github.rodm.teamcity-agent` - Provides tasks to package the Agent-side of a TeamCity plugin.
  * `com.github.rodm.teamcity-common` - Adds the `common-api` dependency to a project to build a library used by both
  the agent-side and server-side plugin components.
  * `com.github.rodm.teamcity-environments` - Adds tasks to download and install a TeamCity Server, to deploy and
  un-deploy plugins to the server, and to start and stop a TeamCity Server and Build Agent.
  
  Refer to the Gradle Plugin Portal for instructions on how to apply the
  {uri-gradle-plugin-portal}plugin/com.github.rodm.teamcity-server[server],
  