Publish job should be smarter about which packages it skips publishing.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | CI Train [cu2d] |
Fix Released
|
Medium
|
Robert Bruce Park | |
Bug Description
Currently, cu2d publish job will silently skip over packages that were previously published (this was by design, as people were complaining in some cases that silos which took multiple attempts to publish were republishing duplicate packages).
However now, if you publish a silo and the package is lost for any reason, and try to republish again, the publication will succeed but silently generate an empty rsync package list for publishing.
There should be some smarter logic involved, like instead of tracking what packages it thinks it has published, it can check the versions at destination and only publish the ones that differ. So instead of skipping packages that it has previously published, it skips the ones that are already confirmed to be in at least -proposed.
Related branches
- PS Jenkins bot: Approve (continuous-integration) on 2015-02-02
- Robert Bruce Park (community): Approve on 2015-02-02
-
Diff: 109 lines (+20/-12)2 files modifiedcitrain/publisher.py (+10/-5)
tests/unit/test_script_publisher.py (+10/-7)
| summary: |
- Needs to be able to force duplicate publishing of packages. + Publish job should be smarter about which packages it skips publishing. |
| Changed in cupstream2distro: | |
| status: | Fix Committed → Fix Released |
Fix committed into lp:cupstream2distro at revision 865, scheduled for release in cupstream2distro, milestone Unknown