The Python VirtualEnv action in Continua is a wrapper around the virtualenv.exe command line. If you're having trouble using the Python VirtualEnv action, please refer to the Command Line Reference. |
Python VirtualEnv action is used to create a virtual environment for python.
The working directory for the pip command line. Leave blank to default to the workspace folder.
The name of the Python package, the URL of the VCS project, a local project directory, or the path/URL of a local/remote package archive to build the wheel for. Leave blank or '.' to search in working folder.
Note that if installing a VCS project in editable mode it must be in the form: vcs+protocol://repo_url/#egg=pkg&subdirectory=pkg_dir. (e.g git+http://git.example.com/MyProject#egg=MyProject). For more information please see Pip Install VCS Support .
If this is ticked, the project is installed in editable mode.
Install packages from the given requirements files. One file path per line. [--requirement]
Visible only if the checkbox 'Install the project in editable mode' is NOT ticked.
Path to the directory where the wheel will be built. Defaults to the working folder. [--wheel]
Visible only if the checkbox 'Install the project in editable mode' is ticked.
The directory to check out editable projects into. The default when running under a virtual environment is “<venv path>\src”. The default for global installs is “<current dir>\src”. [--src]
If this is ticked and exists, the pip executable in the virtual environment scripts folder will be used instead.
The Using drop down is populated by any property collector properties whose namespace matches the pattern defined by the Python VirtualEnv action. The pattern for this action is ^Python.VirtualEnv\..*
. The default property collector searches the environment path for "virtualenv.exe".
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "Python VirtualEnv".
For more in-depth explanations on property collectors see Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
Specify any packages for which binary packages should not be used. [--no-binary]
Note that some packages are tricky to compile and may fail to install when this option is used on them.
Visible only if the option 'Custom List' is selected.
The names of the non-binary packages. One per line.
Specify any packages for which only binary packages should not be used. [--only-binary]
Note that packages without binary distributions will fail to install when this option is used on them.
Visible only if the option 'Custom List' is selected.
The names of the non-binary packages. One per line.
Constrain versions using the given constraints files. One file path per line. [--constraint]
If this is ticked, older binary packages will be used instead of newer source packages. [--prefer-binary]
The amount of information detail to display in the build log. [-qqq | -qq | -q | -v]
The path to a verbose appending log file. [--log]
If this is ticked, the cache is disabled. [--no-cache-dir]
The path to a directory to store the cache data. [--cache-dir]
If this ticked, pip is run in an isolated mode, ignoring environment variables and user configuration. [--isolated]
Specify what to do if path already exists. [--exists-action]
{name}{'.bak' * n}
, where n is some number of .bak
extensions, such that the file didn’t exist at some point. So the most recent backup will be the one with the largest number after .bak
.How many seconds to wait for the action to finish before timing out. The default is 86400 seconds (24 hours).
Tick to continue build on failure marking the action with a warning status.
If this is ticked, any warnings logged will not mark the action with a warning status.
Multiple environment variables can be defined - one per line. These are set before the command line is run.
If this is ticked, environment variable values are written to the build log.
Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and variables.
This checkbox is visible only if the 'Generate system environment variables' checkbox is ticked.
If this is ticked, the values of any variables marked as sensitive will be masked with **** when setting system environment variables. Clear this to expose the values.