Command line git does not provide a way to request a single file from a remote repository. The mode of operation is to fetch the remote repository locally and then checkout the needed file locally.

Lightweight checkout is most useful with higher level git providers like GitHub,, Bitbucket, GitLab, and Gitea. Those higher level providers use a different access technique to request the Jenkinsfile. The git plugin could use the GitRepositoryBrowser information which is optionally provided by the user to attempt to request a single file from a specific branch or revision. That would require writing the code to formulate the request for a single file to each of the repository browser providers and would require that the user must provide that repository browser URL in the job definition. That has not been done.

This is a good enhancement request, though it is not high priority on my list of enhancements.

Since you're using Bitbucket, I believe you could get the benefits of the Bitbucket API by using a multibranch pipeline for that repository, then define it to monitor only a single branch.

Thanks for the info. However I can see a couple of tickets, like this:

Provide lightweight checkout capability for bitbucket to avoid repository clone for multi-branch pipeline jobs

It's in RESOLVED state. I thought that this feature is ready nowadays.

gpilisi it is resolved and works great. It is for multibranch pipelines. The job definition you are describing seems (to me) to not be a multibranch pipeline. It is a pipeline job that is not a multibranch pipeline.

If you're using a multibranch pipeline, then you need to use the Bitbucket provider in that multibranch pipeline rather than using the git provider. The Bitbucket provider is a higher level implementation than the git plugin. It knows it is communicating with Bitbucket and can use the Bitbucket REST API to optimize certain operations (like lightweight checkout and change detection).

It is a multibranch pipeline. And I use Bitbucket Server as a branch source. These are the opitons, I think it is a valid Bitbucket provider, not a simple git repo:

Credentials (for build auth): (our tehcnical user's credential)
Bitbucket Server instance: (the name of our Bitbucket instance which is configured under Configure System / Bitbucket Server Integration)
Project name: (name of the project which contains our repo)
Repository name: (the name of the repo whihc contains the Jenkinsfile too)
Clone from: Primary Server
Behaviours: as mentioned above
etc.

Maybe I choosed a wrong component, trying the bitbucket-branch-source-plugin now.

gpilisi see https://issues.jenkins.io/browse/JENKINS-61493 .

This ticket seems a duplication

JENKINS-61493 is for lightweight checkout in the Bitbucket Branch Source plugin when building the result of merging a pull request. I don't see any git merge command in checkout_log, so this is a different issue.

If the branch source is "Bitbucket server" rather than "Bitbucket", then you are using the Bitbucket Server Integration plugin rather than Bitbucket Branch Source, and this issue is a duplicate of JENKINS-63033, which is currently FIXED BUT UNRELEASED.

Credentials (for build auth): (our tehcnical user's credential)

That setting exists in "Bitbucket server" branch sources (Bitbucket Server Integration plugin), not in "Bitbucket" branch sources (Bitbucket Branch Source plugin). Therefore, I'll go ahead and move this to the atlassian-bitbucket-server-integration-plugin component and resolve as a duplicate of JENKINS-63033.