Merge branch 'id/199' into dev
Delete the SSH key generation command execution.

Instead of executing ssh-keygen command,
deploy the predefined SSH key for the jenkins user.

This commit refs #22.
Store the SSH public and secret key into the encrypted data bags.

Store the SSH public and secret key,
into the encrypted data bags.

Encrypted data bags can keep SSH secret key secret,
at least I believe so!

This commit refs #22.
Deploy the SSH key for jenkins user.

Make sure that the jenkins user has the same SSH key,
in order to git push or git pull.

This commit fixes #22.
Merge branch 'id/22' into dev
Merge branch 'id/199' into dev

Conflicts:
	site-cookbooks/jenkins/recipes/env.rb
Merge branch 'id/199' into dev
Revert "Use the .chef_databag_secret under /home/kazu634."

Secret key should have been on /home/kazu634,
when the Chef is running.
But the secret key will be deployed by Chef itself.

Workaround to this situation is:

  (1) Put the secret key on /home/kazu634 on the Chef executing server.
  (2) Operator manually copies the secret key to /path/to/cookbook directory.
  (3) Executing knife solo blah blah blah

As you know, put the filename of the secret key to .gitignore.

This reverts commit 9d53e1afdffedc60a36bf68146c217f0f836b690.

This commit refs #199.
Add the secret key to .gitignore.

This commit refs #199.
Modify the name of the secret key in .chef/knife.rb.

This commit refs #199.
Modify the README.md to illustrate how to get the secret key.

This commit fixes #199.
Merge branch 'id/199' into dev