Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Done
-
Jenkins 2.235.1
Bitbucket Server Integration plugin 2.0.0
Bitbucket Server 7.1.1
Microsoft Windows
-
-
3.0.0
Description
I tried to migrate a multibranch project from Bitbucket Branch Source Plugin to Bitbucket Server Integration. Before the migration, the Jenkins master read just the Jenkinsfile of each branch from Bitbucket Server over HTTP, and the Jenkins agent then cloned the repository and submodules and pulled Git LFS files. After the migration, the Jenkins master cloned all branches of the repository and pulled Git LFS files. We cannot afford to let the Jenkins master do that, because of time and disk space. I had to revert the migration for this project.
Please change the Bitbucket Server Integration plugin to support lightweight checkout for Jenkinsfile. Perhaps that is part of "SCM API 2.0" JENKINS-62002; I don't know.
Attachments
Issue Links
- is duplicated by
-
JENKINS-62349 Git plugin lightweight checkout copies full repository
-
- Closed
-
- relates to
-
JENKINS-62002 SCM API 2.0 support for Bitbucket Server Integration
-
- Open
-
-
-
- Resolved
-
- links to
Activity
mhenschke_atlassian, what do you mean with "spiking"? I imagine it is not "5. (figuratively, journalism) To discard; to decide not to publish or make public." 
Kalle Niemitalo
added a comment - - edited mhenschke_atlassian , what do you mean with "spiking"? I imagine it is not "5. (figuratively, journalism) To discard; to decide not to publish or make public." kon quite the opposite! I meant spike in the sense of minimal prototyping.
kgiloo
added a comment - what is the aftermath of the issue? Hard to see it clearly here.
I am spiking this ticket at the moment. For anyone watching/waiting on this ticket, are you interested in this feature for pipeline jobs (as opposed to Multibranch Pipeline jobs)? I have been spiking the solution and am not confident a functionally complete solution is possible given how pipeline jobs are implemented, so we're considering just releasing support for Multibranch for now. If anyone is interested in this for pipeline specifically, please file a separate ticket.
EDIT: After a bit more investigation I've confirmed it's impossible for every case, but we can do pipeline so long as the branch selector points to a single branch (no wildcards/selectors)- it appears this is what the GitSCM implementation does so we'll follow suit.