3

Using visual studio online, do I need a separate user for the purpose of ferrying code/builds across machines. I understand that the built in service account builds code and can publish, but with things like Jenkins that require access tokens to retrieve source code (for projects like unity (no we are not able to use unity build)) I find it would be best to have a 'service' account where I can create personal access tokens that isn't tied to any one developer.

Do I need a 'build' user or is there another way to ferry code to Jenkins servers or using personal access tokens for deployment groups?

1

In my opinion, there should always one key per user:

  • Security: If an employee will leave the company then the key could be revoked and the person who left the company cannot trigger builds anymore
  • Access-control and responsibilties: developers from team b are allowed to deploy apps to the production environment of team b, while members of team a are responsible for their own app and are restricted to environment a.
  • while I agree with your points, our development isn't broken into teams with individual responsibility. At some point everyone will need to work on every project. The only people 'approving' a release is the product managers, who can only approve builds that the QA team approves, which will only get builds that the dev team submits through triggering a build and approving it in their sandboxed test environment as point 1, i'm unable to revoke individual PATs as they belong to the individual user account and they create them. Reason for the build account that sys admin/devops manages – xtreampb Feb 8 '18 at 16:08

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.