This plugin allows management of Chef credentials so jobs can execute jobs against a Chef server using those credentials by adding a section to the Jenkins configuration screen to define one or more Chef identities (a combination of the pem key for auth and contents of a knife.rb to define which server to talk to).


Known Limitations

Your knife.rb must have the line client_key "#{current_dir}/user.pem" to find the key file which is being written to disk as user.pem

This DOES NOT install a Chef client on your Jenkins server, that needs to be done separately.


To install the Chef Identity Plugin, Go to your Jenkins' "Plugin Management" section in the adminstration panel.
The latest version will be available.  Install it from there (you should need to restart Jenkins after that).


To verify the plugin is installed properly, go to the Adminstration panel, then in the "Configure System" page you will find the "Chef Identity Management" section:


In your job configuration pages you'll see a new checkbox in the "Build Environment" section that says "Chef Identity Plugin".  When you check the box it will expose a dropdown to select one of the Chef Identities you configured in the administration area.
Then when the job runs, it will write a .chef folder in your Workspace with the user.pem key file and the knife.rb you setup for the selected Chef Identity.

You have the option to remove the .chef folder from the workspace when the build is complete by selecting the Post-build Action of "Delete .chef folder when build is done"

Known issues


1.0.0 (May 12th, 2015)

0.1.4 (May 8th, 2015)

0.1.3 (April 3rd, 2015)

0.1.2 (September 19th, 2014)

0.1.1 (September 19th, 2014)

0.1.0 (September 2014)