Creating a Cookbook Pipeline Using Azure DevOps

Once your project has been created, on the left side click builds in the pipeline menu, then click “New Pipeline” on the right.

In the New pipeline view, on the right under “Where is your code”, click the “Use the visual designer” link.

Select the location of your code as a source and set the default branh for scheduled builds, then click continue.
On the top right, choose empty job when you get to the template screen.
On your pipeline screen, first update your agent pool to use whatever OS you intend to test with. Then in the “Agent Job 1” box, you’ll click the plus sign to the right of the box.

From here, in the “Add tasks” menu on the right, click Marketplace, then in the search box you’ll type Chef. When Chef Integration shows up, click “Get it free”. You’ll be redirected to another screen where you will again click “Get it free”, then you’re prompted to select an Azure DevOps Organization where you would like to install it. After making your selection, click install.
- Once it’s finished installing, you’ll click “Proceed to organization”.
When you get back to the main Azure DevOps page for your organization, click your project, then click pipelines again on the left. You’ll need to go through the steps we went through previously again (ie. Click build, create a new pipeline, click visual designer, etc).
Back in the add tasks menu, search Chef. You will notice that a bunch of Chef tasks come up this time. The first one you want to add is going to be “Install ChefDK”.

From here, you can add other tasks as well. * Many of the testing tasks like cookbook linting use rake. If you do not have a rakefile, and you do not want to create/use one you can simply use the script task and give it a chefdk command like foodcritic .. * If you take this option, make sure to give the full path to the executable.
Once you are satisfied with your steps, and if you want this pipeline to auto execute, click triggers and enable continuous integration.

About Brittany Woods