git-ubuntu

Ubuntu developers cannot stage changes to git-ubuntu uploaders prior to upload

Bug #1844782 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-ubuntu
In Progress
Undecided
Robie Basak

Bug Description

please use per-branch ACLs to grant push access to core-devs.

Specifically, lock and rewoke push access to the usd controlled branches and or tags refs patterns.

Thus allowing to push to e.g. ubuntu-coredev/* refs.

Related branches

~racb/git-ubuntu:staging-branches
Approved for merging into git-ubuntu:main
Andreas Hasenack: Approve
Server Team CI bot: Approve (continuous-integration)
Canonical Server Reporter: Pending requested
Diff: 257 lines (+231/-0)
2 files modified
gitubuntu/importer.py (+102/-0)
gitubuntu/importer_test.py (+129/-0)
Revision history for this message
Robie Basak (racb) wrote :

Thank you for noting this requirement.

Please could you clarify exactly what you expect to happen to a ref after you've pushed it? In other words, what are the use cases you expect enabled by being able to push these refs?

Revision history for this message
Robie Basak (racb) wrote :

(I can guess but I want to be sure that I don't end up implementing something different that doesn't help you)

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

To admit - I really like the suggestion of the basic problem summary of:
- retaining the read-only (for humans) historical data
- allowing custom branches in a defined namespace along it under different ACL
- tools (e.g. git ubuntu) can add additional function/ease-of-access (it is great) but it should as far as possible work without it (that was a design point already so far)

As we have seen in the discussions opinions on details differ vastly, but I really would appreciate if we could find a way that works improving this for everyone while not creating a drawback for existing or planned use-cases.

We might need time and discussions to find that sweet spot in between, but I'd immediately have a few repos that I then would want to unite there instead of the distributed places they have today.

Robie Basak (racb)
tags: added: staging workflow
Revision history for this message
Robie Basak (racb) wrote :

> Please could you clarify exactly what you expect to happen to a ref after you've pushed it?

You didn't answer, so I'm taking my best guess and adapting this bug to track that, since I'm working on this at the moment.

summary: - please use per-branch ACLs to grant push access to core-devs
+ Ubuntu developers cannot stage changes to git-ubuntu uploaders prior to
+ upload
Revision history for this message
Robie Basak (racb) wrote :

Specification up for consultation here: https://discourse.ubuntu.com/t/spec-git-ubuntu-staged-uploads/35409?u=rbasak

ubuntu-devel@ thread: https://lists.ubuntu.com/archives/ubuntu-devel/2023-April/042553.html

Feedback appreciated!

Changed in git-ubuntu:
status: New → Triaged
assignee: nobody → Robie Basak (racb)
Robie Basak (racb)
Changed in git-ubuntu:
status: Triaged → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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