Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Don't rsync .vagrant into the VM #60

Merged
merged 1 commit into from Apr 14, 2014
Merged

Don't rsync .vagrant into the VM #60

merged 1 commit into from Apr 14, 2014

Conversation

sykesm
Copy link
Contributor

@sykesm sykesm commented Apr 11, 2014

The rsync script does not exclude .vagrant when populating the test VM with the code so if you happened to vagrant up the warden test VM from the warden directory, you get your virtual machine copied into your
other virtual machine.

This simply excludes .vagrant from the sync.

The rsync script does not exclude .vagrant when populating the test VM
with the code so if you happened to `vagrant up` the warden test VM from
the warden directory, you get your virtual machine copied into your
other virtual machine.

This simply excludes .vagrant from the sync.
@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/69380976. This repo is managed by the 'Runtime' team.

chou added a commit that referenced this pull request Apr 14, 2014
Don't rsync .vagrant into the VM
@chou chou merged commit a55eec4 into cloudfoundry-attic:master Apr 14, 2014
@sykesm sykesm deleted the dont-rsync-vagrant branch April 15, 2014 11:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants