-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins: 2.479.2
OS: Linux - 6.1.115-126.197.amzn2023.x86_64
Java: 17.0.13 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
cloudbees-bitbucket-branch-source:871.v28d74e8b_4226
-
-
935.0.0
Hello,
The following PR introduced a regression: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/796
Fetch on pull requests has started to fail with the following error:
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. ERROR: Maximum checkout retry attempts reached, aborting
This issue is reproducible on plugin versions from 871.v28d74e8b_4226 to the latest.
We had to roll back the plugin to 866.vdea_7dcd3008e.
It seems that in an attempt to fix the checkout flow for Bitbucket Data Center, Bitbucket Cloud was not properly tested, which has become a major issue for us running Bitbucket Data Center v8.19.5.
As a side note, the Atlassian issue referenced in the comments still hasn't been addressed, so it's unclear why this change was made in the first place.
Your attention to this matter would be greatly appreciated.
Thanks in advance.
- links to
[JENKINS-74980] Pull requests are no longer fetchable
Kyrylo
added a comment - nfalco must be something else. Yet, this PR broke the functionality not just for us, but for quite a few others as well: https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/819
Kyrylo
added a comment - nfalco must be something else. Yet, this PR broke the functionality not just for us, but for quite a few others as well: https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/819 It's not clear how to reproduce the issue.
For the two lines of log could be something related to an authentication issue.
Some authentication issues has been resolved with latest plugin version 933.0.2.
Other authentication issues will be resolved when the git-plugin will be released together with the code in master of bitbucket plugin.
Please let me know if 933.0.2 already resolve this issues or not. And which authentication you are using.
Manjunatha
added a comment - am also facing same issue with plugin Bitbucket Branch Source 933.1.0, i was using thi version 888.v8e6d479a_1730 and working as expected , but after upgrade am facing the same issue , can any tell me what will be the fix
11:05:26 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. 11:05:26 ERROR: Maximum checkout retry attempts reached, aborting
Manjunatha
added a comment - am also facing same issue with plugin Bitbucket Branch Source 933.1.0, i was using thi version 888.v8e6d479a_1730 and working as expected , but after upgrade am facing the same issue , can any tell me what will be the fix
11:05:26 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
11:05:26 ERROR: Maximum checkout retry attempts reached, aborting
Could you share the configuration of the job so that I could reproduce the issue?
Manjunatha
added a comment - HI nfalco
we are using Bitbucket as a source code repo and connecting using Bitbucket server plugin
below is one of the jenkins stage is failing
stage('Calculate Changelog') { echo "CHANGE_TARGET: ${env.CHANGE_TARGET}" // only if this is a PR build when { not { environment name: 'CHANGE_TARGET', value: '' } //expression { return !currentBuild.previousBuild } } steps { // calculate the changeset as being from the PR's target branch script { checkout scm: scmGit( branches: scm.branches, extensions: [ cloneOption(depth: 100, noTags: true, reference: '', shallow: true), changelogToBranch( options: [ compareRemote: 'origin', compareTarget: CHANGE_TARGET ] ) ], userRemoteConfigs: scm.userRemoteConfigs ), changelog: true } } }
you can also check the same issue here https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/819
for now we have downgraded the plugin to 888.v8e6d479a_1730 version
Manjunatha
added a comment - HI nfalco
we are using Bitbucket as a source code repo and connecting using Bitbucket server plugin
below is one of the jenkins stage is failing
stage( 'Calculate Changelog' ) {
echo "CHANGE_TARGET: ${env.CHANGE_TARGET}"
// only if this is a PR build
when {
not { environment name: 'CHANGE_TARGET' , value: '' }
//expression { return !currentBuild.previousBuild }
}
steps { // calculate the changeset as being from the PR's target branch
script {
checkout scm: scmGit(
branches: scm.branches,
extensions: [
cloneOption(depth: 100, noTags: true , reference: '', shallow: true ),
changelogToBranch(
options: [
compareRemote: 'origin' ,
compareTarget: CHANGE_TARGET
]
)
],
userRemoteConfigs: scm.userRemoteConfigs
), changelog: true
}
}
}
you can also check the same issue here https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/819
for now we have downgraded the plugin to 888.v8e6d479a_1730 version Let me try using you pipeline example manjunatha_ns because issue in github is not reproducible.
EDIT: pipeline you post does not compile:
WorkflowScript: 5: Unknown stage section "echo". Starting with version 0.5, steps in a stage must be in a ‘steps’ block. @ line 5, column 9.
stage('Calculate Changelog') {
EDIT2: After fix the pipeline I got this output (no failure, public repository)
Avviato dall'utente unknown or anonymous
Checking out git https://bitbucket.org/nfalco79/test-repos.git into D:\git\bitbucket-branch-source-plugin\work\workspace\nfalco79_test-repos_PR-6@script\b6f429755ea59211e7034a072e91900734ecc2a5b0e29b7e7fd29ed8676743fa to read Jenkinsfile
The recommended git tool is: NONE
Using credentials "test-repos.access.token".
> git.exe rev-parse --resolve-git-dir D:\git\bitbucket-branch-source-plugin\work\workspace\nfalco79_test-repos_PR-6@script\b6f429755ea59211e7034a072e91900734ecc2a5b0e29b7e7fd29ed8676743fa\.git # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.origin.url https://bitbucket.org/nfalco79/test-repos.git # timeout=10
Fetching without tags
Fetching upstream changes from https://bitbucket.org/nfalco79/test-repos.git
> git.exe --version # timeout=10
> git --version # 'git version 2.39.2.windows.1'
using GIT_ASKPASS to set credentials
> git.exe fetch --no-tags --force --progress -- https://bitbucket.org/nfalco79/test-repos.git +refs/heads/feature/issue-819:refs/remotes/origin/feature/issue-819 +refs/heads/master:refs/remotes/origin/master # timeout=10
Merging remotes/origin/master commit bf4f4ce8a3a8d5c7dbfe7d609973a81a6c6664cf into PR head commit e87089f8227afa350808f3fe9a1e3db39be294eb
> git.exe config core.sparsecheckout # timeout=10
> git.exe checkout -f e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
> git.exe remote # timeout=10
> git.exe config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials
> git.exe merge bf4f4ce8a3a8d5c7dbfe7d609973a81a6c6664cf # timeout=10
> git.exe rev-parse "HEAD^{commit}" # timeout=10
Merge succeeded, producing e87089f8227afa350808f3fe9a1e3db39be294eb
Checking out Revision e87089f8227afa350808f3fe9a1e3db39be294eb (PR-6)
> git.exe config core.sparsecheckout # timeout=10
> git.exe checkout -f e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
Commit message: "Try using pipeline from JENKINS-74980"
> git.exe rev-list --no-walk e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
[Bitbucket] Notifying pull request build result
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in D:\git\bitbucket-branch-source-plugin\work\workspace\nfalco79_test-repos_PR-6
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
The recommended git tool is: NONE
Using credentials "test-repos.access.token".
> git.exe rev-parse --resolve-git-dir D:\git\bitbucket-branch-source-plugin\work\workspace\nfalco79_test-repos_PR-6\.git # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.origin.url https://bitbucket.org/nfalco79/test-repos.git # timeout=10
Fetching without tags
Fetching upstream changes from https://bitbucket.org/nfalco79/test-repos.git
> git.exe --version # timeout=10
> git --version # 'git version 2.39.2.windows.1'
using GIT_ASKPASS to set credentials
> git.exe fetch --no-tags --force --progress -- https://bitbucket.org/nfalco79/test-repos.git +refs/heads/feature/issue-819:refs/remotes/origin/feature/issue-819 +refs/heads/master:refs/remotes/origin/master # timeout=10
Merging remotes/origin/master commit bf4f4ce8a3a8d5c7dbfe7d609973a81a6c6664cf into PR head commit e87089f8227afa350808f3fe9a1e3db39be294eb
> git.exe config core.sparsecheckout # timeout=10
> git.exe checkout -f e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
> git.exe remote # timeout=10
> git.exe config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials
> git.exe merge bf4f4ce8a3a8d5c7dbfe7d609973a81a6c6664cf # timeout=10
> git.exe rev-parse "HEAD^{commit}" # timeout=10
Merge succeeded, producing e87089f8227afa350808f3fe9a1e3db39be294eb
Checking out Revision e87089f8227afa350808f3fe9a1e3db39be294eb (PR-6)
> git.exe config core.sparsecheckout # timeout=10
> git.exe checkout -f e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
Commit message: "Try using pipeline from JENKINS-74980"
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Calculate Changelog)
[Pipeline] echo
CHANGE_TARGET: master
[Pipeline] script
[Pipeline] {
[Pipeline] checkout
The recommended git tool is: NONE
Using credentials "test-repos.access.token".
> git.exe rev-parse --resolve-git-dir D:\git\bitbucket-branch-source-plugin\work\workspace\nfalco79_test-repos_PR-6\.git # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.origin.url https://bitbucket.org/nfalco79/test-repos.git # timeout=10
Using shallow fetch with depth 100
Fetching upstream changes from https://bitbucket.org/nfalco79/test-repos.git
> git.exe --version # timeout=10
> git --version # 'git version 2.39.2.windows.1'
> git.exe fetch --no-tags --force --progress --depth=100 -- https://bitbucket.org/nfalco79/test-repos.git +refs/heads/feature/issue-819:refs/remotes/origin/feature/issue-819 +refs/heads/master:refs/remotes/origin/master # timeout=10
> git.exe rev-parse "refs/remotes/origin/feature/issue-819^{commit}" # timeout=10
> git.exe rev-parse "feature/issue-819^{commit}" # timeout=10
Checking out Revision e87089f8227afa350808f3fe9a1e3db39be294eb (refs/remotes/origin/feature/issue-819)
> git.exe config core.sparsecheckout # timeout=10
> git.exe checkout -f e87089f8227afa350808f3fe9a1e3db39be294eb # timeout=10
Commit message: "Try using pipeline from JENKINS-74980"
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
[Bitbucket] Notifying pull request build result
[Bitbucket] Build result notified
Finished: SUCCESS
Dexter
added a comment - I've encountered same issue, and My team find that if we configure the owner( aka Bitbucket project id ) in lower case, the Pull requests can work.
however, in Bitbucket the project ids are actually UPPER CASE... we had to stick with 866 as most of our pipeline jobs are configured with upper case project id and i don't know a way to easily modify them all in batch.
Dexter
added a comment - I've encountered same issue, and My team find that if we configure the owner( aka Bitbucket project id ) in lower case , the Pull requests can work.
however, in Bitbucket the project ids are actually UPPER CASE ... we had to stick with 866 as most of our pipeline jobs are configured with upper case project id and i don't know a way to easily modify them all in batch. Thanks to digger into the issue giving to me an indication where work.
Time ago I read this comment that could be related to this issue. I had already applied in PR 927. It was not released. Can you try master to verify if the bug has been resolved?
Yevhen
added a comment - nfalco The problem still exists in latest version of plugin. Error is the same as in description of the task.
Yevhen
added a comment - nfalco The problem still exists in latest version of plugin. Error is the same as in description of the task. yevhenzamburskyi ok that in latest released plugin version (933.2.x ?) has not been fixed.
I ask if with the incremental build I post in my previous commit the issue has been resolved or not where I should lookaround to see if other compare to fix.
nfalco , I tried the latest build of master branch, issue still exists.
cloudbees-bitbucket-branch-source-934.4.31006.veea_9c6d76f87.hpi
Dexter
added a comment - - edited nfalco , I tried the latest build of master branch, issue still exists.
cloudbees-bitbucket-branch-source-934.4.31006.veea_9c6d76f87.hpi 
Prankevich
added a comment - issue still exists, i also tested. 
Kyrylo
added a comment - I can confirm that the issue is not resolved in the latest available release, 934.4.2.
Kyrylo
added a comment - I can confirm that the issue is not resolved in the latest available release, 934.4.2 . Last chance following the unique suggestion about the root cause of the issue.
This PR replace any exact match of repoOwner (project key i suppose in Bitbucket Data Center) with a match case insensitive.
Now let's say that also if in the past was supported this (strange) use case does not have much sense as the time Bitbucket Data Center decide use request URL as is (case sensitive) the whole integration will not work. The specification of URL says that only hostname are NOT case sensitive, the other part of the URL is case sensitive.
If the incremental version of the PR does not work I suggest to create a bash shell script that replace in every job descriptor file (config.xml) project name from MYPROJECTKEY into myproject and than force Jenkins to reload the configuration from disk.
I've encountered same issue, and My team find that if we configure the owner( aka Bitbucket project id ) in lower case, the Pull requests can work. however, in Bitbucket the project ids are actually UPPER CASE...
dexterwoo something strange to hear, which version are you using of Bitbucket server? My expectation is the that {projecyKey} in the URL is exactly how is defined in the Bitbucket, uppercase. The same is for cloud
> It seems that in an attempt to fix the checkout flow for Bitbucket Cloud, Bitbucket Data Center was not properly tested,
The PR you link is only for DataCenter. Cloud version does not have the concept of mirror