Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

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.

    •  
      request #9656 Deploy a gerrit <-> tuleap bot to ease link between patchset and requests
    Infos
    #9656
    Manuel Vacelet (vaceletm)
    2022-08-25 09:03
    2016-11-13 19:25
    9938
    Details
    Deploy a gerrit <-> tuleap bot to ease link between patchset and requests

    As a first helper (and an excuse to play with Golang...) deploy a hook to automatically add a reference to a gerrit review that reference a request:

    https://tuleap.net/plugins/git/tuleap/tools/gerrit-hooks

    Acceptance criteria:

    • Look for "request #XXX" or "request #XXX" pattern in the whole commit message (subject & body)
    • if there is a corresponding artifact and the reference "gerrit #YYY" is not already present in the follow-up comments, the bot will add "Review gerrit #XXX"
    Empty
    Empty
    Empty
    • [x] enhancement
    • [x] internal improvement
    Empty
    Stage
    Marie Ange Garnier (marieange)
    New
    Empty
    Attachments
    Empty
    References
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2019-01-02 18:13
    Assigning this to myself. I will update the code to use Gerrit stream-events [0] instead of deploying it as a post commit hook. This will ease the deployment process and it is probably more suitable for this kind of work. I also have some other ideas that requires to use stream-events so I will use that as a training opportunity.



    [0] https://gerrit-review.googlesource.com/Documentation/cmd-stream-events.html
    • Assigned to changed from None to Thomas Gerbet (tgerbet)
    User avatar
    Manuel Vacelet (vaceletm)2016-11-14 18:15
    • Original Submission
      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