Admin-only access to rearranging build queue?

Hi,

We are getting enough builds in place that queueing is happening frequently. I thought, "Gee, wouldn't it be nice if I could just drag this build to the front of the queue, and..." HEY, it worked! Nice one.

Then I thought, "I wonder who else can do this, and..." Uh oh, looks like anyone can rearrange the queue.

Is there any way to restrict this feature to TC administrators?

Thanks!
-chris

3 comments

Chris,

As of TeamCity 2.1.1 all registered users can rearrange the build queue and there is no way to limit the ability by configuring TeamCity, for the time being.

Hopefully, this will be possible in TeamCity 3.0, where we plan to implement permission roles for the users. Our current plans regarding the build queue reordering are:

User with "Developer" role can reorder only the builds that belong to the projects, in which user is developer in. This reordering is such that it does not affect position of other projects' builds in the queue.

Will this approach suit your needs?

We are reluctant to restrict a developer from reordering any builds in the queue since developer should have ability to reorder his personal builds that are waiting in the queue.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Hi Yegor,

Thanks for the feedback!

Yes, it does make sense to restrict project mod rights to users who belong to the project. (Will this apply to the "Run" button as well?)

However, w.r.t. re-ordering the build queue, that's more fine-grained (and perhaps confusing to explain) than we need. It DOES make sense to restrict "remove" rights per-project-group. Given that restriction, then within a project, re-ordering can be accomplished by removing and re-submitting...or by just removing, since it appears that removed continuous-builds resubmit themselves anyway (by the way, we'd like to have a "remove" treated as if it were a build attempt, so it doesn't keep spontaneously popping back onto the queue).

For our purposes, only administrators should need to re-order cross-project, in response to prioritization calls (since we also use TeamCity for release builds, not just continuous builds).

With all that said, we don't really want to be in the business of managing queues in an agile environment. We'd rather buy/find/beg more hardware and set up more VMs for build agents! :)

Cheers,
-chris

0

Chris,

We plan to allow assigning users a "role" in a project. The roles will be: Reader (permissions much like current "Guest" user), Developer (like current registered, non-admin user), Project Manager (project-related administration tasks)vand System Administrator (like current admin users).

As to builds readding to queue after manual removing: it is a build trigger who adds a build to the queue. If you want to disable all triggers, you can "pause" a build configuration: it won't be added to the queue by a trigger until set "active" again.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.