I've moved a few old Jenkins jobs to new ones using the pipeline feature in order to be able to integrate the Jenkins configuration within the git repositories. It's working fine but I'm asking myself if there is a way to reduce the number of checkout that happens while building.
Setup
I have a Jenkinsfile in my git repository
#!groovy
node {
stage 'Checkout'
checkout scm
// build project
stage 'Build'
...
}
Problem
When I push to my remote branche BRANCH_1, the multibranch jenkins job is triggered and my understanding is that the following steps happen:
git fetch
for the branch indexing and triggers the job corresponding to my remote branch: BRANCH_1_job
git checkout
to retrieve the Jenkinsfile of the triggered branchcheckout scm
itself. If I don't do it, I can not build my project because no source are available.So for building my branch, I end up with one git fetch
and two git checkout
.
Questions
git checkout
? When I check the official examples, they all make a checkout scm as first step. I would personally think that I don't have to do it because the jenkins job already had to make a checkout to retrieve the Jenkinsfile (so my sources have to be here somehow).Thanks you all
With plain git Jenkins has to do two checkouts: one to get the Jenkinsfile to know what to execute in the job, and then another checkout of the actual repository content for building purposes. Technically Jenkins only needs to load the one single Jenkinsfile from the repo, but git doesn't allow checkout of a single file. Therefore the double checkout cannot be avoided with plain git using the multibranch plugin.
If you host git on Bitbucket or GitHub then you avoid the double checkout by using their specific Jenkins plugins instead of the multibranch plugin.
See the Jenkins plugin site for Bitbucket and GitHub plugins accordingly.
These plugins use the respective Git provider's REST API to load the single Jenkins file. So you technically still have a double checkout, but the first one is a simple REST call to download a single file, rather than doing a full native git checkout of the whole repository.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With