| Extension plugin that allows optionally skipping LFS checkout on master seems like a reasonable approach in this case. A declarative Pipeline job (not multibranch) was assumed (by me anyway) that if it performs a checkout on the master (to get the Jenkinsfile, or for whatever other reason), it would use the same checkout as the agent uses. I'm not sure that my assumption was valid, only that it was my assumption. However, the GitHub Branch Source plugin, the Bitbucket Branch Source plugin, and the Gitea Branch Source plugin all use a REST API call to get the Jenkinsfile (for multibranch at least). If the purpose of the checkout on the master is just to obtain the Jenkinsfile, then I have no objection to an extension plugin that optionally skips LFS checkout on master. |
