The first one is used for personal builds (Remote run or Pre-tested commit) only, i.e. If a build spent long enough in the queue, it won’t be outrun even by builds with higher priority.Īlso note that by default you already have two predefined priority classes - Personal (priority=10) and Default(priority=0). The builds with higher priority will have more chances to appear at the top of the queue however, you shouldn’t worry that the build with lower priority won’t ever run. This setting is taken into account only when a build is added to the queue. You can add as many priority classes as you need, add build configurations to them according to your needs and define the priority in the range -100.100. Naturally, these classes can be configured from the Build Queue page, but note that only users with System administrator role can access these settings. Now you can control build priorities by creating so-called Priority Classes - in two words, a priority class is a set of build configurations with a specified priority. Moreover, since it is implemented as a Build Queue Priorities plugin for TeamCity, it is also available for TeamCity 5.1.x.
In the first TeamCity 6.0 EAP you can find the long-awaited feature - build priorities you asked - we did it.
0 kommentar(er)
