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 install. Leave blank or '.' to search in working folder.
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.
The path to the directory where the packages will be installed. This will not replace existing files/folders, unless the Upgrade option is ticked. [--target]
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 Pip Install action. The pattern for this action is ^Pip\..*
. The default property collector searches the environment path for "pip.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 "Pip".
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]
Visible only if the 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]
Visible only if the 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]
If this is ticked, all specified packages are upgraded to newest available version.
Determines how dependency upgrading should be handled. As of pip version 10.0, the default strategy is 'only-if-needed'. [--upgrade-strategy]
If this is ticked, all packages are reinstalled even if they are already up-to-date. Similar process to pip uninstall -y package && pip install package. [--force-reinstall]
If this is ticked, installed packages and its dependencies are ignored so files are overwritten. [--ignore-reinstalled]
The amount of information detail to display in the build log. [-verbosity=]
Logs the output from running the Cake action without actually performing any tasks. [-dryrun]
Use the latest build of the Roslyn script engine. [-experimental]
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.