Skip to main content

Tuleap 16 est là ! Assistez à l'événement virtuel le 17 octobre à 10h30. Inscrivez-vous ici !

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #1434 Transform an existing repo to a gerrit repo
Actions
Summary
Tuleap Git user
Transform an existing repo to a gerrit repo
I can switch to the Gerrit workflow

Excluded at this point : Restrict read access for Gerrit repos (i.e. Read access will be given to all gerrit "registered-users")
Note: the act of transforming an existing repo to a gerrit repo, will make it become a Gerrit repo, i.e. permissions will no longer be handled in tuleap. No copy of the original repo is made.

Given that the Gerrit instance have been configured with the Tuleap user (non interactive user with ssh key)
And the Gerrit instance has the Tuleap plugin

= I provide an url for the gerrit instance =
Given I choose to transform an existing repo "mobile" of the "Firefox" Project to Gerrit repo
When I provide the URL gerrit.tuleap.net
Then a new Gerrit project "Firefox-mobile" is created on gerrit.tuleap.net

?? Should we
= Ask for confirmation before transforming to a Gerrit repo =
Given I'm at the administration page of a Tuleap repo
When I choose "Transform to Gerrit repo"
Then I am prompted to confirm my choice

= The repo is fully cloned =
And the repo is fully cloned (git clone --bare)

= Permissions are managed in Gerrit =
Given I'm at the administration page of a Tuleap Gerrit repo
Then I can see that all users have read access and the group Gerrit has rewind access
And I can't change read/write and rewind access
And I can't change the description

Empty
Empty
Status
Empty
Done
Development
  • [ ] 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?
Empty
Details
#1434
Johan Martinsson (johan)
2013-01-22 10:11
2012-09-18 12:13
704

References
Artifact links
Referencing story #1434

Artifact Tracker v5

epic #1433 Migrate an existing repo to Gerrit
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2013-01-22 10:11
  • Status changed from Ready (stalled) to Done
  • Checklist set to
  • Permissions set to all_users
  • Category set to
User avatar
Johan Martinsson (johan)2012-09-20 18:43
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Is related to
    • Added:
User avatar
Manuel Vacelet (vaceletm)2012-09-20 15:15
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Johan Martinsson (johan)2012-09-20 11:57
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Manuel Vacelet (vaceletm)2012-09-20 09:45
I don't understand why you insist on "that do not require restrictive Read access" in the "so that". Could you please elaborate ?

Acceptance criteria
-------------------
-> I don't understand what "transforms" means
--> do I still have access to my original gitolite repository ?
--> where is the reference ?
--> who can write in gerrit repo ?
--> who can write in tuleap repo ?


-> "Then I can see that all users have read access the group Gerrit has rewind access"

I think a comma is missing.