Switch last_successful_build to last_successful_build_number

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

Bug Description

There are some comments in the models.py about this: JenkinsJob.last_successful_build and friends are integers, so rename them to last_successful_build_number, e.g., then make get_last_successful_build into a property and massage related functions.

Chris Johnston (cjohnston) wrote :

We normally do this through a query instead of storing the data.

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

Other bug subscribers