Common System Property for a project?

Hi,

We have been using TeamCity extensively and now we are having 50+ projects with 500+ tasks, and found it becoming a time consuming tasks to update indiviual system property on TeamCity tasks.
Therefore I would like to know if there's anyway to assign a common system property on a project, so all task under the project can share the same system property in order to minimize the administration on TeamCity tasks.

Thanks

2 comments

Hello Tomas,

Currently there is no project-level properties in TeamCity, please watch/vote for the feature request http://youtrack.jetbrains.net/issue/TW-4612.

Kind regards,
Marina

0

A use case for project level property:

We currently has TeamCity Setup as:

[Compile  & unit test tasks setup for multiple release in multiple systems to  aid parallel development, approxiately 3 - 4 Releases at a time each  for 8 - 10 systems]

Compile System A
Compile System A Release 2010.Dec
Release System A Release 2011.Jan
Release System A Release 2011.Feb
Unit Test System A Release 2010.Dec
Unit Test System A Release 2011.Jan
Unit Test System A Release 2011.Feb
Wet Test System A Release 2010.Dec
Wet Test System A Release 2011.Jan
Wet Test System A Release 2011.Feb
Duplicate Finder System A Release 2010.Dec
Duplicate Finder System A Release 2011.Jan
Duplicate Finder System A Release 2011.Feb

.
.
.
.
.
.

Compile System H
Compile System H Release 2010.Dec
Release System H Release 2011.Jan
Release System H Release 2011.Feb
Unit Test System H Release 2010.Dec
Unit Test System H Release 2011.Jan
Unit Test System H Release 2011.Feb
Wet Test System H Release 2010.Dec
Wet Test System H Release 2011.Jan
Wet Test System H Release 2011.Feb
Duplicate Finder System H Release 2010.Dec
Duplicate Finder System H Release 2011.Jan
Duplicate Finder System H Release 2011.Feb

[Then  we have multiple environment to deploy to via TeamCity as continous  integration server. The following is our current setup, which takes huge  amount of effort to setup, plus it is very easy to have human errors  when we have to manually manage 300-400 TeamCity Tasks with its own  properties, varaiable, and dependencies back to the artefacts of the  compile tasks!]

Deploy Release 2010.Dec > Project Env 1
Deploy System A Release 2010.Dec > Project Env 1
Deploy System B Release 2010.Dec > Project Env 1
Deploy System C Release 2010.Dec > Project Env 1
Deploy System D Release 2010.Dec > Project Env 1
Deploy System E Release 2010.Dec > Project Env 1
Deploy System F Release 2010.Dec > Project Env 1
Deploy System G Release 2010.Dec > Project Env 1
Deploy System H Release 2010.Dec > Project Env 1

Deploy Release 2010.Dec > Project Env 2
Deploy System A Release 2010.Dec > Project Env 2
.
.
.
.
.
.
Deploy System H Release 2010.Dec > Project Env 2

Deploy Release 2010.Dec > Project Env 3
Deploy System A Release 2010.Dec > Project Env 3
.
.
.
.
.
.
Deploy System H Release 2010.Dec > Project Env 3

Deploy Release 2010.Dec > Project Env 4
Deploy System A Release 2010.Dec > Project Env 4
.
.
.
.
.
.
Deploy System H Release 2010.Dec > Project Env 4

Deploy Release 2010.Dec > SIT
Deploy System A Release 2010.Dec > SIT
.
.
.
.
.
.
Deploy System H Release 2010.Dec > SIT

Deploy Release 2010.Dec > UAT
Deploy System A Release 2010.Dec > UAT
.
.
.
.
.
.
Deploy System H Release 2010.Dec > UAT

Deploy Release 2010.Dec > Pre-production
Deploy System A Release 2010.Dec > Pre-production
.
.
.
.
.
.
Deploy System H Release 2010.Dec > Pre-production

Deploy Release 2010.Dec > Production
Deploy System A Release 2010.Dec > Production
.
.
.
.
.
.
Deploy System H Release 2010.Dec > Production

Deploy Release 2010.Dec > Production Support
Deploy System A Release 2010.Dec > Production Support
Deploy System B Release 2010.Dec > Production Support
Deploy System C Release 2010.Dec > Production Support
Deploy System D Release 2010.Dec > Production Support
Deploy System E Release 2010.Dec > Production Support
Deploy System F Release 2010.Dec > Production Support
Deploy System G Release 2010.Dec > Production Support
Deploy System H Release 2010.Dec > Production Support

[Then we have the same thing for the other 2 - 3 Releases, plus some developement branches / project branches if required:]


Deploy Release 2011.Jan > Project Env 1
Deploy System A Release 2011.Jan > Project Env 1
Deploy System B Release 2011.Jan > Project Env 1
Deploy System C Release 2011.Jan > Project Env 1
Deploy System D Release 2011.Jan > Project Env 1
Deploy System E Release 2011.Jan > Project Env 1
Deploy System F Release 2011.Jan > Project Env 1
Deploy System G Release 2011.Jan > Project Env 1
Deploy System H Release 2011.Jan > Project Env 1

Deploy Release 2011.Jan > Project Env 2
Deploy System A Release 2011.Jan > Project Env 2
.
.
.
.
.
.
Deploy System H Release 2011.Jan > Project Env 2

Deploy Release 2011.Jan > Project Env 3
Deploy System A Release 2011.Jan > Project Env 3
.
.
.
.
.
.
Deploy System H Release 2011.Jan > Project Env 3

Deploy Release 2011.Jan > Project Env 4
Deploy System A Release 2011.Jan > Project Env 4
.
.
.
.
.
.
Deploy System H Release 2011.Jan > Project Env 4

Deploy Release 2011.Jan > SIT
Deploy System A Release 2011.Jan > SIT
.
.
.
.
.
.
Deploy System H Release 2011.Jan > SIT

Deploy Release 2011.Jan > UAT
Deploy System A Release 2011.Jan > UAT
.
.
.
.
.
.
Deploy System H Release 2011.Jan > UAT

Deploy Release 2011.Jan > Pre-production
Deploy System A Release 2011.Jan > Pre-production
.
.
.
.
.
.
Deploy System H Release 2011.Jan > Pre-production

Deploy Release 2011.Jan > Production
Deploy System A Release 2011.Jan > Production
.
.
.
.
.
.
Deploy System H Release 2011.Jan > Production

Deploy Release 2011.Jan > Production Support
Deploy System A Release 2011.Jan > Production Support
Deploy System B Release 2011.Jan > Production Support
Deploy System C Release 2011.Jan > Production Support
Deploy System D Release 2011.Jan > Production Support
Deploy System E Release 2011.Jan > Production Support
Deploy System F Release 2011.Jan > Production Support
Deploy System G Release 2011.Jan > Production Support
Deploy System H Release 2011.Jan > Production Support


Deploy Release 2011.Feb > Project Env 1
Deploy System A Release 2011.Feb > Project Env 1
Deploy System B Release 2011.Feb > Project Env 1
Deploy System C Release 2011.Feb > Project Env 1
Deploy System D Release 2011.Feb > Project Env 1
Deploy System E Release 2011.Feb > Project Env 1
Deploy System F Release 2011.Feb > Project Env 1
Deploy System G Release 2011.Feb > Project Env 1
Deploy System H Release 2011.Feb > Project Env 1

Deploy Release 2011.Feb > Project Env 2
Deploy System A Release 2011.Feb > Project Env 2
.
.
.
.
.
.
Deploy System H Release 2011.Feb > Project Env 2

Deploy Release 2011.Feb > Project Env 3
Deploy System A Release 2011.Feb > Project Env 3
.
.
.
.
.
.
Deploy System H Release 2011.Feb > Project Env 3

Deploy Release 2011.Feb > Project Env 4
Deploy System A Release 2011.Feb > Project Env 4
.
.
.
.
.
.
Deploy System H Release 2011.Feb > Project Env 4

Deploy Release 2011.Feb > SIT
Deploy System A Release 2011.Feb > SIT
.
.
.
.
.
.
Deploy System H Release 2011.Feb > SIT

Deploy Release 2011.Feb > UAT
Deploy System A Release 2011.Feb > UAT
.
.
.
.
.
.
Deploy System H Release 2011.Feb > UAT

Deploy Release 2011.Feb > Pre-production
Deploy System A Release 2011.Feb > Pre-production
.
.
.
.
.
.
Deploy System H Release 2011.Feb > Pre-production

Deploy Release 2011.Feb > Production
Deploy System A Release 2011.Feb > Production
.
.
.
.
.
.
Deploy System H Release 2011.Feb > Production

Deploy Release 2011.Feb > Production Support
Deploy System A Release 2011.Feb > Production Support
Deploy System B Release 2011.Feb > Production Support
Deploy System C Release 2011.Feb > Production Support
Deploy System D Release 2011.Feb > Production Support
Deploy System E Release 2011.Feb > Production Support
Deploy System F Release 2011.Feb > Production Support
Deploy System G Release 2011.Feb > Production Support
Deploy System H Release 2011.Feb > Production Support

[With  project level properties, that may help to minimize duplicate task and  effort to maintain these tasks, the following would be the ideal  structure for deployment with project level property:]

Deploy %Release% > %Environment%
Deploy System A %Release% > %Environment%
Deploy System B %Release% > %Environment%
Deploy System C %Release% > %Environment%
Deploy System D %Release% > %Environment%
Deploy System E %Release% > %Environment%
Deploy System F %Release% > %Environment%
Deploy System G %Release% > %Environment%
Deploy System H %Release% > %Environment%

[Hopefully you guys can come up with a solution as I can see this feature has been rised for 2 years]

0

Please sign in to leave a comment.