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 #18320 native support of pull requests in tuleap branch source jenkins plugin
Actions
Summary
Empty
native support of pull requests in tuleap branch source jenkins plugin

Tuleap pull requests are built automatically as soon as they are created and updated.

tuleap-branch-source Jenkins plugin should be made pullrequests aware:

  • It should look at refs/tlpr/ at initial (and regular) crawls (in addition to refs/heads)
  • We will need to add a head property on the representation returned by /git/:id/pull_requests
  • It will need to call /git/:id/pull_requests and then /git/:id/files with the reference from head property
  • The branch detection mecanism should also be triggered when an event is sent from Tuleap (maybe with a dedicated mecanism when we create a PR)
    • without that we are left with current mecanism for branch detection: regular polling
    • The polling can be made per repository (instead of per project)
  • The PR status should be improved to have a "Pending" state (in addition to "Unknown" atm when it's not "Passed" or "Failed")
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
#18320
Manuel Vacelet (vaceletm)
2021-09-15 15:42
2020-11-18 14:15
3737

References
Artifact links
Empty
Referencing story #18320

Artifact Tracker v5

epic #11662 Pull requests
rel #20934 13.0

Git commit

tuleap/tuleap/stable

Remove useless commented blocks in pullrequest REST tests 37ea942e09
User avatar Thomas Gorka (tgorka) , 2021-02-10 13:41
Add HEAD info in pullrequests representation 82c32657b8
User avatar Thomas Gorka (tgorka) , 2021-02-11 09:32
Introduce pending status for git commits 6f055cf273
User avatar Thomas Gorka (tgorka) , 2021-02-16 09:25
Add permission to set build status 518a8ec04a
User avatar Thomas Gorka (tgorka) , 2021-03-18 15:08
Apply set build status permissions in /git/:id_or_path/statuses/:commit_reference c0c85248e1
User avatar Thomas Gorka (tgorka) , 2021-03-19 12:42
Rename CI Token pane to CI Builds 465b641a42
User avatar Thomas Gorka (tgorka) , 2021-03-22 11:52
Route POST commit status should be public 936dfd16c2
User avatar Thomas Gorka (tgorka) , 2021-03-30 10:32
Add a GET route on /git/{id}/commits/{commit_reference} 1cbe2a824e
User avatar Martin GOYOT (goyotm) , 2021-06-07 17:45
Add a GET route on /git/:id/tree 2b23e6d068
User avatar Martin GOYOT (goyotm) , 2021-06-17 16:36
Add pagination to GET /git/:id/tree 6570a78582
User avatar Martin GOYOT (goyotm) , 2021-06-22 17:45
Fix signature of RepositoryResource::optionsGetTree 3ce0fdacfd
User avatar Thomas Gerbet (tgerbet) , 2021-06-28 15:25
Display settings

Follow-ups

User avatar
Martin GOYOT (goyotm)2020-11-18 14: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
Martin GOYOT (goyotm)2020-11-18 14: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
Manuel Vacelet (vaceletm)2020-11-18 14:36
  • 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
Martin GOYOT (goyotm)2020-11-18 14:29
  • 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
  • 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