Project
TeamCity
Priority
Normal
Type
Feature
State
Open
Assignee
Pavel Sher
Subsystem
Server: Web: Administration
Affected versions
No Affected versions
Fix versions
Backlog
Fixed in build
No Fixed in build
Fixed in builds
no build yet
  • Created by   George Udov
    5 years ago (20 Apr 2007 16:38)
  • Updated by   Yegor Yarko
    16 months ago (23 Jan 2011 22:39)
  • Jira: TW-2449
    (history, comments)
 
TW-2449 More abilities for running specific configurations on specific agents
7
Issue is visible to: All Users
  The issue is visible to the selected user group only
The following features is strongly necessary for us:

1) Agent option, defining, which configurations should be serviced by this agent. I think, agent must have select box, containing two options

(.) Run All compatible configurations EXCEPT (this is default option)
<list of configurations, empty by default>

(.) Run only selected configurations
<list of configurations, empty by default>

2) Build configuration option, defining, which build agents can build this build configuration. Selectbox with two options

(.) Run on all compatible agents, except (this is default option)
<list of agents, empty by default>

(.) Run on only selected agents
<list of agents, empty by default>



Typical usecase:
We have dotTraceTests_amd64 build agent that is necessary to run 4 configurations - dotTrace 2.0 and Main performance and stress tests. This agent must NOT run any other configurations, because
1) running other configurations can affect performance tests results.
2) running other configurations will make running tests less frequent.

On other hand, dotTrace 2.0 and Main performance and stress tests configurations must run ONLY on agent dotTraceTests_amd64.
Comments (3)
 
History
 
Linked Issues (?)
 
Sergey Anchipolevsky
  Sergey Anchipolevsky
20 Apr 2007 17:18
5 years ago
I would propose a more general and flexible solution - backward requirements. That is, not only agents are assessed against configurations' requirements, but vice versa - configurations are also assessed against agent's requirements.

The solution above has a drawback - if we have multiple agents for running dotTrace builds, for example, and we add another dotTrace build, we would have to add this new build on each agent.

My solution allows to avoid repeated reconfiguration.
Eugene Petrenko
  Eugene Petrenko
20 Apr 2007 17:22
5 years ago
I would propose to append some script-like language for requirements definition.

Some subset of the feature can be easily presented as agent-groups.
Kirill Maximov
  Kirill Maximov
05 Jun 2007 16:54
4 years ago
Is not that important after TW-314 has been resolved