Actions
Story #8921
closedStory #8924: As a user, I can manage OSTree repositories
As a user, I can sync an OSTree repository with all of its refs (branches)
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Target Release - OSTree:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 104
Quarter:
Description
-
Create an OSTree repository and distribution.
-
Create an OSTree remote by specifying a URL and a list of refs to sync.
-
Perform a sync using the remote.
-
Update the distribution with the latest repository version.
Updated by dkliban@redhat.com over 3 years ago
- Tracker changed from Issue to Story
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
Updated by ttereshc over 3 years ago
Any comments about publication/distribution would be helpful.
Updated by lmjachky over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
- Sprint set to Sprint 102
Updated by lmjachky over 3 years ago
- Status changed from ASSIGNED to POST
Added by Lubos Mjachky over 3 years ago
Updated by Anonymous over 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 82810bfe5aa4c1039cc9ca1a825d8ed1114c46e2.
Actions
Implement syncing
The sync and upload implementations have multiple codepaths in common. Due to this, many methods were extracted in favour of improving the overall readability.
Also, this commit removes redundant files, tests, methods, and constants that are not required at the moment.
Note that as of this commit, only the archive format is supported for remote repositories. As a result of that, we no longer verify whether content objects are either of type
.file
or.filez
.closes #8921