A project level template or parameter

Dear All,

I was looking for a variable/parameter name which should be available throughout the project. I will explain it more below:

I have a project : PROJECT-A
This project has some build configurations: CONFIGURATION-1,CONFIGURATION-2,CONFIGURATION-3 .... CONFIGURATION-N.

Now I copy PROJECT-A to make PROJECT-B
So, the new project PROJECT-B has all configurations from PROJECT-A:  CONFIGURATION-1,CONFIGURATION-2,CONFIGURATION-3 .... CONFIGURATION-N.

however, I want to change a keyword in few places e.g. checkout rules/build triggering.. etc in all configurations of PROJECT-B..
Is it possible to have a parameter that we set only at once place and that is available to all configurations of the project.

The template only works for a configuration and for me.. changing each configuration for the parameter is also a headache.. So, is there any template with parameter setting on project level..
Or, is there any other way to do this.. through database/api... anything..

Thank you very much..

6 comments
Comment actions Permalink

Hi Kumar

Take a look at project-level parameters that were introduced in version 6.5.

Michael

0
Comment actions Permalink

Thanks a lot Michael,

Its great to know that we have a project level parameter setting now. I will upgrade to 6.5 now.
Just a small question, is there any way to parameterize the fied in build triggering as well. I can see only drop down and it does not look like I can write any parameter name there.

Is there any workaround for this..

thank you very much,
Kumar

0
Comment actions Permalink

Actual version is 7.0.1. You can upgrade directly to it.

Not sure I understand the question on triggers. Which exactly field do you mean?

0
Comment actions Permalink

hi Michael..

thanks again for the prompt response.

I will explain my question below:

In each build configuration, there are various things that can be configured.. for example version control settings, build triggering, dependencies etc..
build triggering configuration means.. setting the build triggering mechanism e.g. scheduling or triggering build after another build finishes etc.
there we can specify the build triggering configuration.. i.e. when to trigger the build..
In my case for example, I specify that build-B should be triggerd after build-A finishes successfully.. now we have to specify build-A in a field while configuring build triggering for build-B.. and that field is a drop-down to choose build-A or any other build configuration... Is there any way to use the parameter in this field..
similar is with dependencies.

I hope you understood my question. If not, please feel free and I will add couple of screenshots with better explanation.

thank you very much again,
Kumar

0
Comment actions Permalink

Hi Kumar

I understand technical side of the question, but would like to know what is a goal behind it.
At the moment triggers cannot be parameterized such way, but I could suggest some alternate approach, if you tell me more about your build procedure.

Thank you.

0
Comment actions Permalink

I created a script to change build dependencies and triggering in teamcity xml file after new project creation so its fine.. thank you very much.. :)

0

Please sign in to leave a comment.