Skip to main content

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 #26799 associate a Tuleap project and a GitLab group
Summary
git administrator
associate a Tuleap project and a GitLab group
Empty

At Tuleap project level, I can associate a GitLab group. This association carry:

  • Artifact closure configuration
  • Branch prefix configuration

Once done:

  • All Gitlab projects existing in the group are made visible in Tuleap.
    • those repositories are created with the defaults defined at project level (artifact closure, branch prefix) but remains independent (each repo can be modified afterward)
  • Subgroups are not supported
  • When a new project is created at GitLab side. As there is no webhook available at GitLab side to trigger the add:
    • A Git Administrator can re-synchronize manually the list of repositories

Synchronization behaviour

  • Only missing project are created (there is no "update" of existing groups)
  • When a project is transferred in another group, nothing happens in Tuleap. The repository remains in Tuleap, no move of project.

When a git administrator removes the synchronization with GitLab, the existing GitLab repositories remains as is in Tuleap.

https://www.figma.com/proto/tifLgfl1OhkXIvv8LIz1Wg/Git---Link-to-a-GitLab-group---story-%2326799?page-id=0%3A1&node-id=5%3A2655&viewport=-2521%2C-3299%2C0.38&scaling=scale-down&starting-point-node-id=5%3A2655

Empty
Empty
Status
SCM/GitLab
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
#26799
Manuel Vacelet (vaceletm)
2022-11-08 15:22
2022-05-17 13:21
28705

References
Referencing story #26799

Artifact

epic #26798 GitLab / Tuleap: management of groups
story #26800 create a gitlab repository from Tuleap
rel #27178 14.2
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2022-11-08 15:22

Nightly synchronization is removed from the initial acceptance criteria because the whole synchronization feature proved to be already hard enough and we need to limit the overrun.

Plus we identified that nightly will be more challenging than initially thought because of rate limit on API that can be put in place.

Let's see how the feature is used first. Nightly synchro should naturally come back if there is enough usage of the feature.

  • 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
  • Status changed from On going to Done
User avatar
Manuel Vacelet (vaceletm)2022-09-06 17:08
  • 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)2022-09-06 16:49
  • 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
Benjamin Dauton (bdauton_enalean)2022-06-30 15:58
  • 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