[PATCH] tests: add Vagrantfile to automate running them on virtual machines
Kevin Bullock
kbullock+mercurial at ringworld.org
Fri Jul 11 22:22:42 CDT 2014
On Jul 11, 2014, at 5:43 PM, Matt Mackall <mpm at selenic.com> wrote:
> On Sat, 2014-07-05 at 19:42 +0300, anatoly techtonik wrote:
>> # HG changeset patch
>> # User anatoly techtonik <techtonik at gmail.com>
>> # Date 1404567148 -10800
>> # Sat Jul 05 16:32:28 2014 +0300
>> # Branch stable
>> # Node ID 65a3d892ee2f147d536ffc5a0af84432fc18eb48
>> # Parent 2392b9e1936628faeec818368169a68b1fadd95f
>> tests: add Vagrantfile to automate running them on virtual machines
>>
>> Now running tests is as easy as:
>> 1. install vagrant
>> 2. $ vagrant up
>> 3. $ vagrant ssh -c ./run-tests
>>
>> diff -r 2392b9e19366 -r 65a3d892ee2f Vagrantfile
>> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
>> +++ b/Vagrantfile Sat Jul 05 16:32:28 2014 +0300
>
> Is there a reason for this to be in the root rather than contrib/?
We may want to put it in a 'contrib/vagrant/' directory and set an ignore rule on '^contrib/vagrant/.vagrant/'. Vagrant is one of those tools that likes to leave turds in its "project root".
pacem in terris / мир / शान्ति / سَلاَم / 平和
Kevin R. Bullock
More information about the Mercurial-devel
mailing list