Skip to content
← General

I suggest you ...

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

TeamCity Plugin Customizable Workspace Name

Is it possible to specify the name of the workspace that is created for a build configuration when using Plastic 5.x with TeamCity 8.x? Currently a workspace is dynamically created with the name tc### where the number actually correlates to the primary key of the vcsroot_instance stored in the TeamCity configuration. What this means is that every time we update the parameter for the build configuration that contains the name of the Plastic branch we wish to use, Plastic tries to create a new workspace. This is a problem because the same folder is being used and already is designated for a different workspace, and Plastic throws an error reflecting that problem. We use the parameter to specify our branch name because multiple build configurations share the same branch name due to our code base spanning multiple repositories. We can't combine our repositories due to legacy issues.

1 vote
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Göran Wallgren commented  ·   ·  Report

    When editing a VCS Root that uses the Plastic plugin, you can specify "Workspace directory" . The description says: "Provide path to a directory on TeamCity server where the workspace should be created. Leave blank to use default path (will use one workspace per VCS configuration)".

    With this, I think the options for customizing the workspace path is already in place. Thereby this uservoice could be closed?

  • Göran Wallgren commented  ·   ·  Report

    When using "server-side VCS checkout mode", I think you can specify where the workspace should be created.

    Also, since 5.4.16.712 the Plastic plugin also supports "agent-side VCS checkout mode". In the latter mode, the workspace currently gets a default name of "plasticscm_15" and is located under the TeamCity "Build Checkout" directory (teamcity.build.checkoutDir). However, I've been told by Codice staff that this will soon be changed so that the checkout is done directly in the "Build Checkout" directory without the extra sub-directory.

    The two modes are explained here:
    https://confluence.jetbrains.com/display/TCD9/VCS+Checkout+Mode