Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

pipeline (4) Versions 2.3.0

Installs/Configures a Jenkins based chef delivery pipeline

Berkshelf/Librarian
Policyfile
Knife
cookbook 'pipeline', '~> 2.3.0'
cookbook 'pipeline', '~> 2.3.0', :supermarket
knife cookbook site install pipeline
knife cookbook site download pipeline
README
Dependencies
Changelog
Quality

pipeline cookbook

Continuous delivery pipeline for Chef.

Overview

As you commit Chef artifacts to git (i.e. cookbooks, data bags, environments and roles) the pipeline will test and load them into Chef automatically.

The pipeline is Jenkins based and relies on a git repository of your Chef items of the following structure:

chef_repo/Berksfile
chef_repo/environments/
chef_repo/roles/
chef_repo/data_bags/

Description

  • Berksfile:
    • Contains all the cookbooks in your project.
    • Used to generate cookbook jobs for cookbooks that need testing
    • Used to upload community cookbooks that don't need testing
    • assumes there is a 'community' or external group of cookbooks you want to deliver to the Chef server
  • environments/: Directory of environment files in a format accepted by knife upload
  • roles/: Directory of role files in a format accepted by knife upload
  • data_bags_/: Directory of data bag files in a format accepted by knife upload

Jobs

Both of the following job types listen on their respective repositories and upload to Chef when changes are committed to git.

Once the pipeline is up and fully flushed out you will have N+1 cookbooks in your Jenkins dashboard, where N is the number of cookbooks you have that require testing. And the +1 is the chef_repo job which is responsible for uploading all the roles, environments and data bags as well as cookbooks that bypass testing.

Chef Repo Job

  • Uploads roles, environments, data bags and community cookbooks from the git repo to the Chef server

Cookbook Jobs

  • Lint and test the respective cookbook
  • Upload respective cookbook from git to the Chef server

Instructions

Note that there is a dependency between the chef-client and a Jenkins job. The cookbook jobs are generated by the chef-client from the chef_repo that is kept up to date by Jenkins. Because of this the chef-client will need to run twice on initial set up of the pipeline server to flush out all of the cookbook jobs.

Try it!

From the command line, run the following twice:

kitchen converge centos-7

Now check out your local CD pipeline demo on http://localhost:9090

Example Berksfile

from https://github.com/stephenlauck/pipeline-example-chef-repo/blob/master/Berksfile

source "https://supermarket.chef.io"

group :community do
  cookbook 'jenkins'
  cookbook 'java'
  cookbook 'apt'
  cookbook 'yum'
  cookbook 'emacs'
  cookbook 'git'
  cookbook 'chef-zero'
  cookbook 'chef-dk'
end

cookbook 'pipeline', git: 'https://github.com/chef-solutions/pipeline.git'
cookbook 'gitlab', git: 'https://github.com/chef-solutions/gitlab.git'

Production Notes

Update the following to a chef_repo of your own:

default['pipeline']['chef-repo']['url'] = "https://github.com/stephenlauck/pipeline_chef.git"

  • There is a .chef folder in the jenkins user's home. You will need to put an appropriate .pem file in there for a pipeline user with admin rights to Chef.
  • This uses the Chef embedded version of Ruby for knife and Berkshelf etc.
  • Since this uses Berkshelf for cookbook uploads, all cookbook versions are frozen by default. Failure to update the metadata version number should result in a failed job.
  • Since this uses Berkshelf to upload your cookbooks to Chef, there is an expectation that every cookbook to be tested contain the usual Berkshelf workflow tools such as kitchen, vagrant and berks.

Platform

  • Ubuntu 12.04
  • CentOS 6.5

Authors

Dependent cookbooks

chef-dk >= 0.0.0
sudo >= 0.0.0
emacs >= 0.0.0
chef-zero >= 0.0.0
jenkins >= 0.0.0
java >= 0.0.0
git >= 0.0.0
yum >= 0.0.0
apt >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

pipeline Cookbook CHANGELOG

This file is used to list changes made in each version of the pipeline cookbook.

v2.3.0 (06/13/2015)

  • use same chef-client path even with chefdk installed
  • fix errors when installing jenkins plugins
  • fix FC errors for syntax checking

v2.1.0 (09/05/2014)

  • Add lint recipe to setup lint testing on jobs

v1.1.0

  • pin dependent cookbook versions
  • job commands as partials

v1.0.0

  • broke out recipes from default into berkshelf, jenkins, jobs

  • added build command attr in order to step thru cookbook job -- may belong in wrapper

  • added LWRP for creating chef_server configuration ala berks config

  • added chef-zero support

Collaborator Number Metric
            

2.3.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

2.3.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

2.3.0 failed this metric

FC064: Ensure issues_url is set in metadata: pipeline/metadata.rb:1
FC065: Ensure source_url is set in metadata: pipeline/metadata.rb:1
FC066: Ensure chef_version is set in metadata: pipeline/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: pipeline/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

2.3.0 failed this metric

pipeline does not have a valid open source license.
Acceptable licenses include Apache-2.0, apachev2, Apache 2.0, MIT, mit, GPL-2.0, gplv2, GNU Public License 2.0, GPL-3.0, gplv3, GNU Public License 3.0.

No Binaries Metric
            

2.3.0 passed this metric

Publish Metric
            

2.3.0 passed this metric

Supported Platforms Metric
            

2.3.0 failed this metric

pipeline should declare what platform(s) it supports.

Testing File Metric
            

2.3.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

2.3.0 passed this metric