Publisher tool option to only change the database, not the archive

Bug #4730 reported by Celso Providelo
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Unassigned

Bug Description

This option should allow the user to run publisher script in a kind of "archive-dry-run", i.e., the only the database will get modified at the end of the process the package archive will remain the same or would be dispensable. This option would be very useful for buildfarm tests and other preliminary process until we get satisfied with the job performed by our set of tools and also publisher itself should be able to recover the package archive to the normal state after several runs in this mode, since all the history will be perfectly stored in the database. Does it make sense ?

Tags: lp-soyuz
Revision history for this message
Daniel Silverstone (dsilvers) wrote :

Yep, it's on my TODO. I will hopefully get around to it once I've finished the rest of the ftpmaster tools.

Changed in launchpad-upload-and-queue:
assignee: nobody → dsilvers
status: New → Accepted
Changed in qprocd:
assignee: dsilvers → nobody
Revision history for this message
Robert Collins (lifeless) wrote :

I think this is done already, and if not, as the driver was for testing, will close - its not something we intend to schedule for itself.

Changed in launchpad:
status: Triaged → Incomplete
Changed in launchpad:
status: Incomplete → Won't Fix
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 4730] Re: Publisher tool option to only change the database, not the archive

Julian says this would be a dangerous option to have, and that this is YAGNI.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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