Merge lp:~cjohnston/ubuntu-ci-services-itself/goldenpackages into lp:ubuntu-ci-services-itself
Proposed by
Chris Johnston
Status: | Merged |
---|---|
Approved by: | Chris Johnston |
Approved revision: | 55 |
Merged at revision: | 56 |
Proposed branch: | lp:~cjohnston/ubuntu-ci-services-itself/goldenpackages |
Merge into: | lp:ubuntu-ci-services-itself |
Diff against target: |
53 lines (+1/-6) 3 files modified
ticket_system/project/migrations/0001_initial.py (+0/-2) ticket_system/project/models.py (+0/-1) ticket_system/project/tests.py (+1/-3) |
To merge this branch: | bzr merge lp:~cjohnston/ubuntu-ci-services-itself/goldenpackages |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Francis Ginther | Approve | ||
Review via email: mp+199673@code.launchpad.net |
Commit message
Change from seeded binaries to tested sources
To post a comment you must log in.
I think I understand how BinaryPackage is going to be used. The golden set of packages == all the BinaryPackage objects. +1
How does this handle a ticket that requests adding or removing a package, but the ticket ultimately fails. For example:
1) The golden package list is [A, B, C].
2) A ticket is created which includes a request to add package [D, E] and remove [A].
3) An image is built and tested with [B, C, D, E].
4) The test and ticket fails.
5) The golden package set remains [A, B, C].
I'm not seeing how the ticket holds the binary package information (but perhaps that's for a different MP).