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.

    •  
      request #11789 Webhook are triggered for each changeset during xml import
    Actions
    Infos
    #11789
    Marie Ange Garnier (marieange)
    2018-07-12 16:43
    2018-07-09 18:11
    12380
    Details
    Webhook are triggered for each changeset during xml import
    How to reproduce:
    have a tracker with webhook
    use patch /artifacts/{id} route to move your artifact

    => import will trigger webhook for each changeset and slower the query
    Trackers
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2018-07-12
    Attachments
    Empty
    References
    Referencing request #11789

    Git commit

    tuleap/tuleap/stable

    Webhooks are no more processed during project XML import 4d30e9995f
    User avatar Yannis ROSSETTO (rossettoy) , 2018-07-12 14:52
    Referenced by request #11789

    Artifact Tracker v5

    rel #11517 10.3

    Other

    gerrit #12005
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-07-12 16:43
    Integrated in Tuleap 10.2.99.193.
    • Status changed from Under review to Closed
    • Reported in version set to development
    • Connected artifacts
    • Close date set to 2018-07-12
    User avatar
    Yannis ROSSETTO (rossettoy)2018-07-12 11:22
    A patch is under review: gerrit #12005

    The choice made here was to no process the webhooks in the case where notifications are not processed.
    If there is a need to have webhook in some case after the XML import, it could be done in a next contribution.
    • Status changed from New to Under review
    User avatar
    Manuel Vacelet (vaceletm)2018-07-09 21:25

    We need to think carefully about the behaviour, what would be expected here ?

    The parallel with email notifications is good, shall we trigger an event on both trackers ? and what should be the event after all ?