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 #11947 Jenkins could not determine exact tip revision of XXX
    Actions
    Infos
    #11947
    Yurili (yurili)
    2018-07-26 15:46
    2018-07-26 15:09
    12571
    Details
    Jenkins could not determine exact tip revision of XXX
    After changing the jenkins ref spec to +refs/tlpr/*/head:refs/remotes/* (see picture 1). The CI-Pipeline couldn't finish the first stage, because it doesn't find the branch name anymore (see logfile 1). What goes wrong? With the original ref spec (+refs/heads/*:refs/remotes/@{remote}/*) everything works fine except that Jenkins is trigger while pushing and not after creating a pull request.

    References: https://docs.tuleap.org/user-guide/pullrequest.html#integrate-with-jenkins
    Continuous Integration
    10.2
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Acknowledged
    Empty
    Attachments
    By Yurili (yurili)
    (61 kB)
    2018-07-26 15_02_18-CI-Pipeline_my_modules Config [Jenkins].png
    picture 1 - jenkins config
    By Yurili (yurili)
    (5 kB)
    log1.txt
    logile 1 - protocol
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Yurili (yurili)2018-07-26 15:46
    last edited by: Yurili (yurili) 2018-07-26 15:57
    Jenkins itself is 2.121.2 and the Blue Ocean plugin is 1.7.1.
    I'll check the Jenkins bug. >> Okay. They have the same error message, but I couldn't adapt their problem and answer on my situation.