-
New Feature
-
Resolution: Unresolved
-
Minor
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline
it seems that the initial git clone is actually works on the jenkins controller
Started by user Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10
also in my local PC I can perform git checkout to this PR
git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'
But When the jenkins is trying to perform checkout scm on a different agent (node)
stage('Generate') { node ('linux') { checkout scm }
or
pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm
note: in declarative pipeline the jenkins will try automtically to perform checkout scm on the agent node and it will failed too.
it's getting the following error:
> git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE
why the step checkout SCM is not respecting the git Discover other refs?
another way to workaround this?
[JENKINS-64719] checkout scm on the agent does not respect git 'Discover other refs' in multibranch pipeline
Description |
Original:
I'm trying to use the git plugin in order to detect pull requests from my git repository which is located in azure devops
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When I'm doing {code:java} stage('Generate') { node { checkout scm } {code} it's getting the error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout scm* is not respecting the git Discover other refs ? |
New:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When I'm doing {code:java} stage('Generate') { node { checkout scm } {code} it's getting the error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? |
Description |
Original:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When I'm doing {code:java} stage('Generate') { node { checkout scm } {code} it's getting the error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? |
New:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When I'm doing {code:java} stage('Generate') { node ('linux') { checkout scm } {code} it's getting the error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? |
Description |
Original:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When I'm doing {code:java} stage('Generate') { node ('linux') { checkout scm } {code} it's getting the error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? |
New:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Attachment | New: image-2021-01-27-10-11-45-680.png [ 53894 ] | |
Description |
Original:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Description |
Original:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Description |
Original:
I'm trying to use the git plugin to detect pull requests from my git repository which is located in Azure DevOps
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Description |
Original:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to nodejs pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Description |
Original:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works on the jenkins controller {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
Description |
Original:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works on the jenkins controller {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |
New:
I'm trying to use the git plugin to detect *pull requests* from my git repository which is located in *Azure DevOps*
I'm using the following configuration in Multibranch Pipeline !image-2021-01-26-19-08-26-320.png! !image-2021-01-27-10-11-45-680.png! it seems that the initial git clone is actually works on the jenkins controller {code:java} Started by user Dor Saidon Replayed #11 > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 ERROR: Could not determine exact tip revision of pull/74/merge; falling back to nondeterministic checkout Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] library Loading library pipeline-library@master Attempting to resolve master from remote references... > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git ls-remote -h -- https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Found match: refs/heads/master revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d The recommended git tool is: NONE using credential jenkins-token > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://user@dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching without tags Fetching upstream changes from https://user@dev.azure.com/<account>/<project>/_git/<repo> > git --version # timeout=10 > git --version # 'git version 2.11.0' using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- https://user@dev.azure.com/<account>/<project>/_git/<repo> +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d (master) > git config core.sparsecheckout # timeout=10 > git checkout -f eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 Commit message: "align to pipeline" > git rev-list --no-walk eeeacb692d0fc5e23c0c5ba66123fdbf95bbac0d # timeout=10 {code} also in my local PC I can perform git checkout to this PR {code:java} git checkout pull/74/merge # output: Branch 'pull/74/merge' set up to track remote branch 'pull/74/merge' from 'origin'. Switched to a new branch 'pull/74/merge'{code} But When the jenkins is trying to perform *checkout scm* on a different agent (node) {code:java} stage('Generate') { node ('linux') { checkout scm } {code} or {code:java} pipeline { agent { label 'linux' } stages { stage('Initialize') { steps { checkout scm{code} note: in declarative pipeline the jenkins will try automtically to perform *checkout scm* on the agent node and it will failed too. it's getting the following error: {code:java} > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://dev.azure.com/<account>/<project>/_git/<repo> > git config remote.origin.url https://dev.azure.com/<account>/<project>/_git/<repo> # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git --version # 'git version 2.11.0' > git config --get remote.origin.url # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress -- origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/merge:refs/remotes/origin/pull/*/merge # timeout=10 > git rev-parse refs/pull/74/merge^{commit} # timeout=10 [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } 19:08:21 [Pipeline] // ansiColor [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of pull/74/merge Finished: FAILURE {code} why the step *checkout SCM* is not respecting the git Discover other refs? another way to workaround this? |