Skip to content

Separate provisioning into a separate build step #2

Closed
rtyler opened this Issue Mar 8, 2012 · 0 comments

1 participant

@rtyler
Owner
rtyler commented Mar 8, 2012

We're currently running vagrant up (effectively) which will do a provision by default if it's configured.

Really I don't think this should be done in the set up, but rather as a separate build step.

The reasoning behind this is that we might want to pull down separate artifacts or otherwise prepare the Jenkins workspace before running the provision.

@rtyler rtyler added a commit that closed this issue Mar 13, 2012
@rtyler Move provisioning into a dedicated build step
This may prove to be controversial, but I'd like to set up additional things in
my local environment before I run the provision

Fixes #2
fbdfeec
@rtyler rtyler closed this in fbdfeec Mar 13, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.