Ticket's final published_versions is not updated
Bug #1530866 reported by
Łukasz Zemczak
This bug report is a duplicate of:
Bug #1508186: Use bileto instead of rsync for copy2distro script..
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bileto |
New
|
Medium
|
Unassigned |
Bug Description
For history and diagnostics we need to know which packages and versions got published with which request. For this purpose the published_versions field got created in both the original jenkins json files and then in bileto. Currently in bileto this field is broken and not updated at all. We worked-around that for now by using the 'published_
We would need published_versions to show the final state of what packages got published in the end.
To post a comment you must log in.
This is effectively a duplicate of https:/ /bugs.launchpad .net/bileto/ +bug/1508186 in the sense that fixing that one would also fix this one. Long story short, I'm not happy with the way published_versions field works on the ticket (too easy to clobber old data with new data during publishing). That's why I switched it to being a field on the comments, so that there'd be an immutable record of what was published and when.
But, as you say, parsing through every comment on every ticket is expensive and requires many API requests. So I'd prefer to make an entirely new db table to contain publishing records and use that to replace the weird rsync thing we're doing now.