We have a build system, which fetches the sources and executes build commands. At present a dedicated person (build master) does the fetching with her personal account in the source control system.

We'd like to automate the build process. How can access to the source control system be secured?

I see an option to create a "shared account" (let's call it buildmaster) so that the user who is authorised to do the build would use a script with buildmaster's credentials (in our case - username/password) to fetch the sources. How could then buildmaster's password be made available to only those users who are authorised to run (production) builds?

  • Without knowing what the authenticating software is, we cannot answer this, but you've not told us anything about it. – symcbean Mar 14 '17 at 21:14

Your build is probably executed by a non-interactive program. In Windows, for example, it would run as a service.

The service would be configured with a service account, which has its own user ID and password. In your case the user ID would be "buildmaster."

If you have a need for a human being to trigger the build, there would need to be some means to tell your service to start a build, e.g. a UI. You would not want to use the buildmaster account directly.

| improve this answer | |
  • Thank you. Yes, just as I wrote in the question, a service account is needed. Then, how could the secret part of its credentials (password, or a private key) be protected? – Konstantin Shemyak Mar 15 '17 at 19:10
  • 1
    Depends on your O/S. See this link for Windows, and this tech note on some options for managing the passwords. – John Wu Mar 15 '17 at 19:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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