Rename .nova-venv to .venv.
This simplifies a number of Jenkins jobs which currently, other than directory names, could be the same for all OpenStack projects. By renaming the virtualenv directory, the redundant Jenkins virtualenv build and copy jobs can be eliminated. Change-Id: Ieaf1dac3207ecb34b911c7edcd2086809abdf49e
This commit is contained in:
parent
2f5ae4ab62
commit
6e46cc7e04
|
@ -9,6 +9,7 @@ build/*
|
|||
build-stamp
|
||||
nova.egg-info
|
||||
.nova-venv
|
||||
.venv
|
||||
*.sqlite
|
||||
*.log
|
||||
po/*.pot
|
2
.mailmap
2
.mailmap
|
@ -25,6 +25,8 @@
|
|||
<jake@ansolabs.com> <jake@markupisart.com>
|
||||
<jake@ansolabs.com> <admin@jakedahn.com>
|
||||
<jaypipes@gmail.com> <jpipes@serialcoder>
|
||||
<jeblair@hp.com> <james.blair@rackspace.com>
|
||||
<jeblair@hp.com> <corvus@inaugust.com>
|
||||
<jmckenty@gmail.com> <jmckenty@joshua-mckentys-macbook-pro.local>
|
||||
<jmckenty@gmail.com> <jmckenty@yyj-dhcp171.corp.flock.com>
|
||||
<jmckenty@gmail.com> <joshua.mckenty@nasa.gov>
|
||||
|
|
2
Authors
2
Authors
|
@ -55,7 +55,7 @@ Hisaki Ohara <hisaki.ohara@intel.com>
|
|||
Ilya Alekseyev <ilyaalekseyev@acm.org>
|
||||
Isaku Yamahata <yamahata@valinux.co.jp>
|
||||
Jake Dahn <jake@ansolabs.com>
|
||||
James E. Blair <james.blair@rackspace.com>
|
||||
James E. Blair <jeblair@hp.com>
|
||||
Jason Cannavale <jason.cannavale@rackspace.com>
|
||||
Jason Koelker <jason@koelker.net>
|
||||
Jay Pipes <jaypipes@gmail.com>
|
||||
|
|
|
@ -96,7 +96,7 @@ Grab the code from GitHub::
|
|||
|
||||
Running unit tests
|
||||
------------------
|
||||
The unit tests will run by default inside a virtualenv in the ``.nova-venv``
|
||||
The unit tests will run by default inside a virtualenv in the ``.venv``
|
||||
directory. Run the unit tests by doing::
|
||||
|
||||
./run_tests.sh
|
||||
|
@ -130,7 +130,7 @@ If all goes well, you should get a message something like this::
|
|||
To activate the Nova virtualenv for the extent of your current shell session
|
||||
you can run::
|
||||
|
||||
$ source .nova-venv/bin/activate
|
||||
$ source .venv/bin/activate
|
||||
|
||||
Or, if you prefer, you can run commands in the virtualenv on a case by case
|
||||
basis by running::
|
||||
|
|
|
@ -42,7 +42,7 @@ function process_option {
|
|||
esac
|
||||
}
|
||||
|
||||
venv=.nova-venv
|
||||
venv=.venv
|
||||
with_venv=tools/with_venv.sh
|
||||
always_venv=0
|
||||
never_venv=0
|
||||
|
|
Loading…
Reference in New Issue