Call Pytest with additional pip install arguments

[sanski]

Expected / Requested Behavior

Make an additional paramater in the pytest task to pass additional pip install arguments to the pytest task. This is useful, when your packages are not on the default pypi.org repository, but on another package repository or behind a proxy.

Actual Behavior

The current pytest task calls "pip install -r requirments.txt". This default to looking those packages up in pypi.org.

Steps to Reproduce the Problem

There is no problem to reproduce, this is just an additional parameter to make the pytest task more flexible.

Additional Info

Proposed additional argument. Example call in the pipeline:

params:
  - name: PYTHON
    value: "3.9"
  - name: ARGS
    value: "-rfs"
  - name: PIP_INSTALL_ARGS
    value: "--index-url=$(params.nexusUrl)$(params.nexusHosted) --extra-index-url=$(params.nexusUrl)$(params.nexusProxy) --trusted-host=$(params.nexusUrl) --timeout=3600"

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vinamra28]

/remove-lifecycle stale

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.