Should I set up a shared account in our CI infrastructure to make it easier to use?
My team uses CI infrastructure. When a developer first sets up a build he must enter his source control credentials so that the server can access the code. Thus the build is "tied" to a particular developer. I personally like this--I think each build should have a maintainer and that the maintainer's credentials should be used.
Occasionally things break because of account permissions issues, such as when a developer changes his password. I think this is because we don't manage user accounts well.
Some team members think that we should have a shared source control account to prevent this kind of problem. All builds could use the same shared account for accessing source control.
I am opposed to this because of the security implication. Since the shared account's credentials would be common knowledge, anyone could use it with no traceability to a person. We would not be able to limit access to certain parts of source control to certain individuals.
Would a common source control account for running CI builds actually be a problem? How do other small software shops manage this?