Artifact "be blocked to push on a git repository after gerrit migration (story #2227)" has more than one parent: "Gerrit: Import an existing repo in tuleap (epic #1463)", "Gerrit miscallaneous (epic #1461)"
When more than one parent, we cannot display rest of hierarchy.

story #2227 be blocked to push on a git repository after gerrit migration

Artifact

Summary

As a

developer

I want to *

be blocked to push on a git repository after gerrit migration

So that

I don't mess-up the gitolite repo because it is fetched from gerrit

Acceptance criteria

Once a repository is pushed to gerrit, I can no longer push on it on Tuleap

AttachmentsEmpty

CC listEmpty

Status

CategoryEmpty

Status *Done

Development

Checklist

[ ] Does it involves User Interface?
[ ] Are there any mockups?
[ ] Are permissions checked?
[ ] Does it need Javascript development?
[ ] Does it need a forge upgrade bucket?
[ ] Does it need to execute things in system events?
[ ] Does it impact project creation (templates)?
[ ] Is it exploratory?

Technical informations

The idea is to set permissions as it would be done on the interface (no modifications on read, write to nobody, rewind to nobody).
Be careful to push permissions to gerrit before changing them on tuleap side otherwise you would push a repository where nobody can push.

Details

Artifact ID#2227

Submitted ByManuel Vacelet (vaceletm)

Last Modified On2013-04-15 11:41

Submitted On2013-01-22 10:22

Rank1220

Permissions

Restrict access to this artifact for the following user groups:

References

Is related to

Artifact links

Empty

Reverse artifact links

Epics

Parent

Artifact ID	Project	Tracker	Summary	Status	Last Update Date	Submitted By	Assigned to
epic #1463	Tuleap	Epics	Gerrit: Import an existing repo in tuleap	Closed	2013-13-08 08:57	Johan Martinsson (johan)
epic #1461	Tuleap	Epics	Gerrit miscallaneous	Closed	2016-05-09 17:29	Johan Martinsson (johan)