Hi Eric, You need to understand first what exactly you want to be run and at which point. >From the quick glance it could be running Chef on already provisioned server (use SSH to do that when you need it) or creating a new server in the cloud for running tests etc on it. (It's likely there are some more usecases I'm missing here). Not sure what is the most recommended way to do that with Jenkins (I'd love to hear about that too) but we use Vagrant for spinning up servers for integration tests. Jenkins kicks Vagrant to create a new server. You can then use Vagrant Chef provisioners or whatever you like to setup your server. After the test run is finished we just retrieve the test reports from the server and terminate it. Hope that makes sense for you.
Regards, Timur вторник, 27 января 2015 г., 21:21:33 UTC+3 пользователь eric...@rocketmail.com написал: > > Currently I am deploying application code to our target environments using > the Build Pipeline plugin. It is a visualization tool for managing a chain > of upstream and downstream jenkins jobs. We want to incorporate chef > scripts into our deployment process for setting up the initial servers and > verifying their configuration. For example, we want to be able to install > tomcat, java and other packages in a consistent programmatic way. > > Does it make sense to incorporate this pieces into my build pipeline along > with the build steps for deploying the application code & liquibase DB > changes. What is the preferred method for incorporating setting up the > application server to be able to accept our application code. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a2577cce-e697-4dff-b0b6-f0a4185006fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
