jenkinsci / jenkinsci/subversion-plugin

[JENKINS-54125] Jenkinsfile lightweight checkout help doesn't match behaviour - polling and changelog work without checkout scm

Open
#1,492 1 comment 0 reactions 0 assignees View on GitHub
component:subversion-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

Hi, I'm using the new Lightweight checkout feature in the SVN plugin to retrieve a Jenkinsfile.  The checkout works correctly and I can see on my Jenkins master it's no longer doing a full checkout.

The help for the 'lightweight checkout' feature states the following:

"If selected, try to obtain the Pipeline script contents directly from the SCM without performing a full checkout. The advantage of this mode is its efficiency; however, you will not get any changelogs or polling based on the SCM. (If you use checkout scm during the build, this will populate the changelog and initialize polling.) Also build parameters will not be substituted into SCM configuration in this mode. Only selected SCM plugins support this mode."

I don't have a checkout scm step in my Jenkinsfile, however the polling and changelog both appear to be working correctly (which doesn't match the help above). 

 Does the help documentation need updating?

I'm also not clear on how/why I get a get a full checkout in my build steps without an explicit  checkout scm step when using the lightweight checkout e.g.

pipeline


{
     agent \{ label "pipeline" }

     stages {

         stage("Stage1") {

             steps


{

                 echo "running stage1 on $NODE_NAME"

             }

        }

     }

}

 

[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkout

 

All of the documentation seems to show a checkout scm step when Jenkins is configured to get the pipeline script from SCM.  Why am I getting a checkout without this, and is there a way to prevent it i.e. just checkout the Jenkinsfile?

 If this isn't an appropriate place to ask these questions please advise where I should raise this.  Thanks, Rich.

---
Originally reported by richardm, imported from: Jenkinsfile lightweight checkout help doesn't match behaviour - polling and changelog work without checkout scm


  • status: Open
  • priority: Minor
  • component(s): subversion-plugin
  • label(s): Jenkinsfile, SVN
  • resolution: Unresolved
  • votes: 1
  • watchers: 3
  • imported: 20251212-090250

Raw content of original issue

Hi, I'm using the new Lightweight checkout feature in the SVN plugin to retrieve a Jenkinsfile.  The checkout works correctly and I can see on my Jenkins master it's no longer doing a full checkout.

The help for the 'lightweight checkout' feature states the following:

"If selected, try to obtain the Pipeline script contents directly from the SCM without performing a full checkout. The advantage of this mode is its efficiency; however, you will not get any changelogs or polling based on the SCM. (If you use checkout scm during the build, this will populate the changelog and initialize polling.) Also build parameters will not be substituted into SCM configuration in this mode. Only selected SCM plugins support this mode."

I don't have a checkout scm step in my Jenkinsfile, however the polling and changelog both appear to be working correctly (which doesn't match the help above). 

 Does the help documentation need updating?

I'm also not clear on how/why I get a get a full checkout in my build steps without an explicit  checkout scm step when using the lightweight checkout e.g.

pipeline


{
     agent \{ label "pipeline" }

     stages {
         stage("Stage1") {
             steps


{

                 echo "running stage1 on $NODE_NAME"

             }

        }
     }
}

 
[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkout
 

All of the documentation seems to show a checkout scm step when Jenkins is configured to get the pipeline script from SCM.  Why am I getting a checkout without this, and is there a way to prevent it i.e. just checkout the Jenkinsfile?

 If this isn't an appropriate place to ask these questions please advise where I should raise this.  Thanks, Rich.

environment

```
Jenkins 2.89.2. Subversion plugin 2.12.1. Jenkins master on Ubuntu 14.04 LTS and Jenkins slaves on Ubuntu 16.04 LTS.

Java version on master:

java version "1.8.0_151"

Java(TM) SE Runtime Environment (build 1.8.0_151-b12)

Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)

Java version on slaves:

java version "1.8.0_181"

Java(TM) SE Runtime Environment (build 1.8.0_181-b13)

Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.