Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M monitor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cto
  • monitor
  • Issues
  • #33
Closed
Open
Issue created Sep 11, 2018 by Karmanya Aggarwal@karmanya.aggarwalDeveloper

Python and Pip paths need to be hardcoded into gitlab.yml/setup.sh

Currently python and pip installed on UAT are by default python2

Thus if any project deploys python 3 projects that needs to install multiple packages, then setup.sh ends up using python2 unless the setup.sh explicitly mentions the python 3 path for python/pip for example a setup.sh file trying to install a library in a python3 project would typically include a requirements.txt file and pip install -r requirements.txt - this would invoke python2's pip and the project on UAT would throw import errors.

Conversely if the setup.sh file mentions /home/ubuntu/anaconda3/bin/pip install -r requirements.txt the python3 version of pip is used.

Assignee
Assign to
Time tracking