Development/Test TeamCity Server and Licensing

My team is currently using TeamCity 9 Professional with enough additional build agent licenses to support our ~70 build configurations.

In the interests of not breaking our production build system, we would like to have our build system developers use a local TeamCity Server installation to create and modify build configurations and test them before transferring the changes to the real build server.

The biggest issue that we are running into is that the personal development/test TeamCity servers can only run with 20 build configurations without purchasing additional licenses. In order to actually run and test our build configurations we would need each build system developer to have as many build agent licenses as our real TeamCity server.

We had thought of having developers only import a subset of our project hierarchy into their personal TeamCity servers at one time to keep the total number of build configurations under 20, but that significantly complicates the development workflow and would require some awkward restructuring of our projects.

Is our only option here to purchase additional licenses for development/test environments? Would this be an appropriate use of Evaluation Licenses, and if so is there any process in place that could help us keep those up to date for our developers rather than requiring manual license requests every 60 days?

6 comments
Comment actions Permalink

Hi Dean,

There are two options for test server: 1. Buy new license; 2. use Evaluation license.
The Evaluation license can be obtained only once for each major TeamCity version. If you need to extend/repeat the evaluation, you need to contact our sales department. It is not possible to use Evaluation license on daily basis without renewal.

When buying many licenses you are welcome to contact our sales for available volume discounts.

0
Comment actions Permalink

We are in the same situation having a large (> 100 build configurations) setup for our TeamCity production server.
A TeamCity test server has only 100 build configurations, so it will not by default be able to use the same setup as the production server.

If i understand the above correctly, then we will have to ask Jetbrains for Evaluation licenses so that the test server can have the required number of build configurations. That seems like quite a hassle to manage, so i was wondering if there are other options ?

 

0
Comment actions Permalink

Please take a look at fx. Atlassian licenses model  - https://confluence.atlassian.com/jirakb/how-to-get-a-jira-developer-license-744526918.html.
They offer a Developer License for each product one buy, so the above problems can be solved. May JetBrains could consider a similar solution?

0
Comment actions Permalink

Hi Bo and Gordon,

 

there is a request in our tracker for that: https://youtrack.jetbrains.com/issue/TW-23208 . Please add your comments in there, further discussion in this topic won't help.

0
Comment actions Permalink

The url gives me

404: Nope, can't find it! Despite our best efforts, there's nothing here to show you with the URL you requested. Most likely the URL is invalid or you don't have permissions to access the page.

0
Comment actions Permalink

Thanks for the heads up, I hadn't realized that the issue is kept private due to the sales nature of the discussion in there. I have left a remark in it and added a link to this issue, just wanted to mention that it is under consideration

0

Please sign in to leave a comment.