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 #9181 Add an api to allow ci to send build status updates and add an event which will be raised when the api is called
    Actions
    Summary
    Empty
    Add an api to allow ci to send build status updates and add an event which will be raised when the api is called
    the pullrequest plugin can print the state of the build for the pullrequests.

    The api would be called by any CI to notify the progress of a build of a specific commit on a specific branch.
    The git plugin would then notify via a system event of this notification.
    It would allow us to update information and display it in the proper pull requests.
    Empty
    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
    #9181
    Adrien H. (sogiadrien)
    2016-06-24 14:58
    2016-05-23 17:14
    9459

    References
    Artifact links

    Requests

    Referencing story #9181

    Artifact Tracker v5

    request #9247 CI token pane is unusable
    rel #8983 8.16
    request #9259 POST /git/{id}/build_status is declared as hybrid but ask for a basic authentication

    Git commit

    tuleap/tuleap/stable

    Merge 'gerrit #9181' into stable/master 1bf9b6395d
    User avatar Thomas Gerbet (tgerbet) , 2016-06-13 16:17
    story #9181 [Plugin Git] CI build status a34079e8bd
    User avatar Adrien H. (sogiadrien) , 2016-06-13 15:53
    request #9247: CI token pane is unusable due to a missing column in the database d5e10af7a9
    User avatar Thomas Gerbet (tgerbet) , 2016-06-13 18:16
    Merge branch 'stable' into burning_parrot 1b044acfce
    User avatar Nicolas Terray (nterray) , 2016-06-14 08:50
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-06-01 14:50
    Concerning the authorization issue it has been decided that the proposed solution is good enough for now and we will deal with it during one of the first steps of the next phase.
    User avatar
    Thomas Gerbet (tgerbet)2016-05-30 13:47
    How do you make the difference between a "classical" user and a CI user?

    A user should not have the possibility to make his patch pass the CI just because he wants to and have the possibility to call the REST route.
    User avatar
    Adrien H. (sogiadrien)2016-05-30 10:59
    • 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
    User avatar
    Adrien H. (sogiadrien)2016-05-30 10:46
    • 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