Question

EDIT: This feature has been implemented: Access Tokens

Now that Kiln allows a virtual user to be assigned permissions on a Kiln project, is it possible to use a virtual user for build server activities? If so, since a virtual user does not have a password, how does one set up the security on the build server to utilize the virtual user?

If this isn't possible, what is the purpose in assigning project permissions to a virtual user?

Case FC2048341

Answer 1

Unfortunately it's not currently possible. There were some conversations about this feature here (see use case 2 and comments). And as far as I remember Fog Creek Team were going to consider this feature, but there is still no information whether it will be implemented.

EDIT:
In general, virtual users are intended for assigning cases to a group of people. And there is a description when you create an user:

A virtual user can't log on and doesn't use up a license. You can create virtual users to assign a case to a group of people. For example, you could create an "Up For Grabs" virtual user that owns a case until someone assigns it to themselves.assigns it to themselves.

Also, recently Tyler has covered here new feature of Kiln 2.3 - ability to assign code reviews to virtual users.

I assume, that the main purpose and benefit of assigning permissions for virtual users is the same as for normal users - you can restrict access to specific repositories. So, you just can't make a mistake and assign case or review to a wrong user (e.g. if you have several teams and each of them uses their own "Up For Grabs" virtual user).

Answer 2

Depending on what your needs are for your build server as well as your environment and how well you are able to restrict access to Kiln (if you host it yourselves), Kiln release 2.2.27 added the ability to make a repository Public so that anyone can pull from it. This won't let you push any built artifacts or tags back in, but you can at least build.

Answer 3

A full Normal or Admin user is required to access Kiln. Virtual and Community users cannot push / pull / clone / etc.

Using the KilnAuth extension, you can log into Kiln once on your build server and the cookie hg receives will keep the build server logged in. Any pushes your build scripts perform will show up under that user, but you can set the username for commits to anything you want. We use "autobuild" as shown in this screenshot.

Answer 4

Joel needs an even fancier office. For the love, please put in a built in user called "ROBOT". We need it for build servers. We should NOT have to pay a license for this crap...at least just give us all a free one...problem solved.