top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Testing and credentials best practices?

+1 vote

How do you deal with tests (both on dev machine and Jenkins) that need credentials (such as AWS keys)?.

I know of the following methods:
1. Test user with known (stored in source control) limited credentials
2. ~/.secrets (or any other known location) RC file which is not in source control
3. Credentials service (such as ZooKeeper) accessed only from VPN
4. Credentials pre user encrypted (gpg) and stored in source control

What method are you using? Are there any best practices in the subject?

posted Apr 20, 2014 by Amit Parthsarthi

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button
I've done several of these. Another option that may work in some contexts is to mock the test altogether; have a server that simulates whatever you needed credentials for, and accepts a key of all zeroes or equivalent. Obviously that key can happily go into the source code :)

1 Answer

+1 vote

We've been looking at using etcd to store credentials (essentially the same solution as zookeeper). It seems like the right way to go.

So far, my impression of etcd is "neat, promising, not ready for prime time yet" (to be fair, the etcd folks don't claim it's stable yet). ZooKeeper at least has the advantage of being in production use for a long time, so it should be pretty bullet-proof.

answer Apr 20, 2014 by Naveena Garg
Similar Questions
0 votes


I'm using Github as a repository for my project. I have integrated Jenkin locally. Currently, I'm building Jenkin manually. I need to automate the Jenkin process whenever pushing the changes into the repository

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.