TeamCity 9.x Documentation

[Documentation for Previous Versions]

Icon

You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the [listing] to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Version is used in several places:

  • for changes collecting
  • for patch construction
  • when content of the file is retrieved from the repository
  • for labeling / tagging

TeamCity does not show Versions in the UI directly. For UI, TeamCity converts a Version to its display name using VcsSupport#getVersionDisplayName(String, VcsRoot).

...

Code Block
class SomeVcsSupport implements VcsSupport {
...
  public SomeVcsSupport(VcsManager manager) {
    manager.registerVcsSupport(this);
  }
...

Wiki Markup
{show-if
:mode
edit

Challenges

TODO (detecting versions, grouping changes into modifications, handling checkout
=edit}
h2. Challenges

TODO (detecting versions, grouping changes into modifications, handling checkout rules...)
{show-if}

Server side caches

By default, server caches clean patches created by VCS plugins, because on large repositories clean patch construction can take significant time. If clean patches created by your VCS plugin must not be cached, you should return true from the method VcsSupport#ignoreServerCachesFor(VcsRoot).

...

To create agent side checkout, implement

Tc javadoc
classjetbrains.buildServer.agent.vcs.CheckoutOnAgentVcsSupport
version4.x
in the agent part of the plugin. Also server side part of your plugin must implement
Tc javadoc
classjetbrains.buildServer.AgentSideCheckoutAbility
version4.x
interface.



...

See Also: