Organize my teamcity

Hi,

I'm testing TeamCity 6.5 for my business and I would like to have  more details before buying this software.

I have 3 products which I  compile on 3 platforms (PC, Mac and Linux) and I have 4 versions per  product

and I'm not even talking about 3 modes of compilation (Debug,  Beta, and Release).

My first question is what is the best way to organize  my teamcity for all the products and platforms that I have:

1 project per  version and per product = 3*4 = 12 projects or

1 project per version = 4  projects or

something else?

I'm lost in the multitude of available  solutions. Any advice would be greatly appreciated. Thank you in  advance.

Best regards.

Stéphane

8 comments
Comment actions Permalink

Hi Stephane,

I would recommend 3 projects - one per  product. You can have your 3 platforms*3 modes*4 versions=36 builds in  each project. This will provide visibility into each product's health.  You can also then manage TeamCity roles/permissions based on the product  if you have different teams working on each product.

There are also multiple ways to organize compilation:  you can either have a build with a single compilation step or a build  with multiple compilation steps.

My 2 cents. Welcome to TeamCity. Great product.

Oleg.

0
Comment actions Permalink

Hi Stephane,

I would recommend 3 projects - one per  product. You can have your 3 platforms*3 modes*4 versions=36 builds in  each project. This will provide visibility into each product's health.  You can also then manage TeamCity roles/permissions based on the product  if you have different teams working on each product.

There are also multiple ways to organize compilation:  you can either have a build with a single compilation step or a build  with multiple compilation steps.

My 2 cents. Welcome to TeamCity. Great product.

Oleg.

0
Comment actions Permalink

Hi Stephane

Projects are the way to group related build configurations together, so it depends on number of configurations and personal choice.
Here at JetBrains we usually create a project per product version. For next release a project is just cloned from previous one. Old projects are archived later.

0
Comment actions Permalink

thanks for all your answers

I simplified my configuration for starting
I created one projet per version and per product
I created one configuration per plateforme (3 configurations)
Each configuration compil my product in debug and release

I still have one question for my testing in Teamcity
Currently my process for building my product is a script that reads a parameter file

Teamcity can he creating a parameter file?

Thanks for your answers

Stéphane
Sorry for my medium english

0
Comment actions Permalink

Sorry, not sure I understand the question.
It woulв be great if you provide some examples what kind of parameter files are you using.

Thanks
Michael

0
Comment actions Permalink

My script reads a parameter file of twenty lines. this file is a ini file under windows


example

Key1 = value1

Key2 = value2


My question is how can I modify this remote file in that directory on my agent from within my web browser.


I know I can put the "Environment Variables" in my setup configuration but I would like to avoid having to change it with each modification. That is I prefer to modify my file instead of my configuration.


If I can not, is it possible to take a file that is on the local disk of my client and upload it to my remote agent



Thank you for your answers


Stéphane

0
Comment actions Permalink

Stephane,

The best solution is to put this file right into your version control system.

0
Comment actions Permalink
Thank you Mickael for  your answer

Stéphane
0

Please sign in to leave a comment.