Episode
Integrating Chef Into Your Visual Studio Team Services Builds
When developing and testing a cookbook, it is recommended that a build pipeline is used to ensure recommendations and standards are being followed and that tests are always run. This also avoids the problem where someone can push to a cookbook on the Chef server and also has to commit to source control.
Watch this webinar as we show you how, using the Chef extension for VSTS, this pipeline can be built in VSTS so that on every commit all the cookbook tests are run and optionally Test Kitchen tests. You will see that only when these have passed will the release phase publish the cookbook to the Chef Server.
Using Chef with VSTS, each developer is now held to the same standards as the versions of the cookbook governed by the build pipeline.
When developing and testing a cookbook, it is recommended that a build pipeline is used to ensure recommendations and standards are being followed and that tests are always run. This also avoids the problem where someone can push to a cookbook on the Chef server and also has to commit to source control.
Watch this webinar as we show you how, using the Chef extension for VSTS, this pipeline can be built in VSTS so that on every commit all the cookbook tests are run and optionally Test Kitchen tests. You will see that only when these have passed will the release phase publish the cookbook to the Chef Server.
Using Chef with VSTS, each developer is now held to the same standards as the versions of the cookbook governed by the build pipeline.
Video URL
HTML iframe
Have feedback? Submit an issue here.