Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51516

TFS PR commit not found

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • tfs-plugin
    • None

      I have a setup where a VSTS build starts a jenkins job. I use that build for building pull requests. I configured the refspec according to the instructions. 

      Everything worked fine, but recently the tfs plugin builds the wrong PR. In the logs I see this message

      skipping resolution of commit <commit id>, since it originates from another repository

      After that statement, it falls back to a previous VSTS PR branch and builds the wrong commit.

       UPDATE

      I found out that it works if I enter the git url in the jenkins build with only lowercase characters. As soon as I use uppercase characters in the git url, it thinks that it's a different repository. I don't know if the actual issue is in this plugin or in the git plugin.

          [JENKINS-51516] TFS PR commit not found

          Marco Bachmann created issue -
          Marco Bachmann made changes -
          Description Original: I have a setup where a VSTS build starts a jenkins job. I use that build for building pull requests. I configured the refspec according to the instructions. 

          Everything worked fine, but recently the tfs plugin builds the wrong PR. In the logs I see this message
          {code:java}
          skipping resolution of commit <commit id>, since it originates from another repository
          {code}
          After that statement, it falls back to a previous VSTS PR branch and builds the wrong commit.

                      		New: I have a setup where a VSTS build starts a jenkins job. I use that build for building pull requests. I configured the refspec according to the instructions. 

          Everything worked fine, but recently the tfs plugin builds the wrong PR. In the logs I see this message
          {code:java}
          skipping resolution of commit <commit id>, since it originates from another repository
          {code}
          After that statement, it falls back to a previous VSTS PR branch and builds the wrong commit.

           *UPDATE*

          I found out that it works if I enter the git url in the jenkins build with only lowercase characters. As soon as I use uppercase characters in the git url, it thinks that it's a different repository. I don't know if the actual issue is in this plugin or in the git plugin.
          Ian Williams made changes -
          Assignee Original: redsolo [ redsolo ]

            Unassigned Unassigned
            nerumo Marco Bachmann
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: