•  
     
    story #17182 reference tuleap artifacts in gitlab merge requests
Summary
Empty
reference tuleap artifacts in gitlab merge requests
Empty

Follow-up of art #17181:

  • When a developer creates a Merge Request (MR) in gitlab, gitlab triggers a webhook in Tuleap
  • The webhooks creates a cross-reference "gitlab-mr" is the MR contains a reference like tuleap-XXXX (case insensitive) and XXXX is an artifact id in the project.
  • In artifact view, the cross reference is displayed (table)
  • The Tuleap Pull Requests are updated to match the same display.

Link back from GitLab to Tuleap:

  • When a MR is open with a tuleap-XXXX reference, Tuleap create a comment on the MR with a link back to Tuleap
  • When a commit (as of art #17178) contains a tuleap-XXXX reference, Tuleap create a comment on the commit with a link back to Tuleap

Those link back need to update the way the GitLab token is handled at Tuleap side. One should use a project token and this token must be persisted in Tuleap DB

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
#17182
Manuel Vacelet (vaceletm)
2021-02-04 14:00
2020-10-07 11:22
3414

References

Follow-ups

User avatar
  • 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
gerrit #21334 integrated into Tuleap 12.4.99.47

  • 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 Ready (stalled) to On going