Isolate and lock vrange/python dependencies
What does this MR do?
This commit changes the vrange/python installation so that it utilizes the pipenv package manager to isolate its packages and ensure that the builds are reproducible i.e. locks the packages in a Pipfile.lock. This fixes the root cause of the issue described in gitlab-org/gitlab#385219 (closed).
What are the relevant issue numbers?
Fixes gitlab-org/gitlab#385219 (closed)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer