Story #1158
closed
As a user, I can force full/fresh publish of rpms and not do an incremental publish
Status:
CLOSED - CURRENTRELEASE
- Tracker changed from Issue to Story
- Subject changed from skip_fast_forward option for publish to As a user, I can force full publish of rpm repos
- Groomed set to No
- Sprint Candidate set to Yes
- Tags Easy Fix added
- Has duplicate Story #1098: Support a 'forced' metadata regeneration added
- Subject changed from As a user, I can force full publish of rpm repos to As a user, I can force full/fresh publish of rpms and not do an incremental publish
- Description updated (diff)
- Parent issue set to #1683
- Blocks Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publish added
I suggest a different setting name, but this looks like a good behavior to add.
The fast-forward feature causes some parts of the normal publish to be skipped. Having a setting to skip that skipping is just a little awkward. Do two skips cancel each other out?
Instead I suggest a setting like "force_full", or something similar. It focuses on what the user wants, not what they don't want.
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Sprint/Milestone set to 19
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Platform Release set to 2.9.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone deleted (
19)
Also available in: Atom
PDF
.
Add --force-full flag to publish command
re #1158 https://pulp.plan.io/issues/1158