[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection

[vorobieva...@yandex.ru (JIRA)]

Title: Message Title

Alexander Vorobiev commented on JENKINS-33273   Re: Optimize Jenkinsfile loading and branch detection It would be great to have one reference repo at master or one per node. Nearby nodes could also clone from master neither from GitHub. 1st fetch can be done on the reference repo at master 2nd fetch or checkout on master to retrieve Jenkinsfile can be avoided with use of git archive. Something like: git archive --format=tar --remote=file://"${REF_CLONE}"/.git ${GIT_BRANCH}:Jenkinsfile | tar xf - 3rd fetch on slave can be done from local reference repo, that itself might be cloned from reference repo at master. This can be done with git-worktree. Yet 3rd fetch on slaves can be optimized in Jenkinsfile with use of manually created local reference repo in ${WORKSPACE}/../ref_repo. A bit dirty, but still works: def ws = pwd() checkout([ $class: 'GitSCM', branches: [[name: "**/${env.BRANCH_NAME}".replaceAll('PR-','pr/')]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: false, reference: "${ws}/../ref_repo/.git", shallow: false]], submoduleCfg: [], userRemoteConfigs: [[refspec: '+refs/pull/*/head:refs/remotes/origin/pr/*', url: 'g...@github.com:${ORG}/${REPO}.git']] ]) Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.