Helipad

make sure when stacks are updated in cupstream2distro that the database reflects the change

Bug #1186418 reported by Chris Gagnon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Helipad
Won't Fix
High
Francis Ginther

Bug Description

We need to make sure when projects are updated (moved from one stack to another or removed) in cupstream2distro that the database reflects the change in both the stack and the project pages.

Currently this is untested

Revision history for this message
Francis Ginther (fginther) wrote :

Also be sure to handle the case of a new project being added to a stack (which can happen several times in a week).

Allan LeSage (allanlesage)
Changed in helipad:
importance: Undecided → High
Chris Johnston (cjohnston)
Changed in helipad:
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
Allan LeSage (allanlesage) wrote :

cjohnston brings up an interesting wrinkle: do changes propogate backwards in time? fginther believes a change should be reflected as a delete and create.

Revision history for this message
Allan LeSage (allanlesage) wrote :

Francis promises to list some use cases :) .

Revision history for this message
Francis Ginther (fginther) wrote :

Update use cases:
 - new stack with new projects
 - new stack with existing projects (or mix of old and new)
 - stack with new release
 - new project in existing stack
 - new child jobs for existing project
 - new builds for existing jobs

Revision history for this message
Francis Ginther (fginther) wrote :

I'm working on this now.

Changed in helipad:
assignee: nobody → Francis Ginther (fginther)
status: Triaged → In Progress
Francis Ginther (fginther)
Changed in helipad:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.