For non-apt-installables, use requirements.txt

Bug #1179552 reported by Allan LeSage on 2013-05-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Allan LeSage

Bug Description

Not all of our requirements can be installed via apt-get, and so we install them piecemeal during the Jenkins build, e.g.--instead just use requirements.txt: update requirements.txt and test, and then ensure that the deployment works in the Jenkins job.

Chris Johnston (cjohnston) wrote :

Remember that for production everything has to be installed via apt-get

Allan LeSage (allanlesage) wrote :

cjohnston informs me that they're also using requirements.txt, just validate that we don't have any lurking requirements, add any to existing. requirements.txt.

Changed in helipad:
status: New → Incomplete
status: Incomplete → Invalid
status: Invalid → New
assignee: nobody → Allan LeSage (allanlesage)
importance: Undecided → Low
Changed in helipad:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers