Bug 830956

Summary: RFE: ability to keep repository histories or package changes as version control
Product: [Retired] Pulp Reporter: Jim Perrin <jperrin>
Component: user-experienceAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: low    
Version: MasterCC: ericlake, rbarlow, skarmark
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 00:48:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jim Perrin 2012-06-11 19:11:09 UTC
Description of problem:

Add version control to repository state for history, rolling back, etc. 

Version-Release number of selected component (if applicable):


How reproducible:
Never. Doesn't currently exist. We'd like it to.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Currently the only method to maintain a repository version is to create a repository clone. 

Expected results:
Ability to update, roll back, and identify repository version information. 

Additional info:

Comment 1 Eric Lake 2012-06-11 22:43:26 UTC
This would be a really nice feature to have. I would envision something like the way git can tag a release. Or even the history functionality in yum may work as well. Once you know that the packages in your copy of the repo are good then you can create a tag that you can easily roll back to if needed. 

Where I work we have build systems that build code for our products all day every day. It would be nice to be able to get back to a know good repo if we find an issue.

Comment 2 Brian Bouterse 2015-02-19 00:48:43 UTC
Moved to https://pulp.plan.io/issues/173