jenkinsci / jenkinsci/workflow-multibranch-plugin

[JENKINS-45686] UI for SCMBinder.USE_HEAVYWEIGHT_CHECKOUT

Open
#467 2 comments 0 reactions 0 assignees View on GitHub
component:workflow-multibranch-plugin imported-jira-issue priority:minor resolution:unresolved ux
Dominant language
Java
Stars
87
Forks
131
PR merge metrics
No merged PRs in 30d

Description

Currently the only way to do a heavy weight checkout is to set a system property for Jenkins java arguments. (viewable only from source code)

'-Dorg.jenkinsci.plugins.workflow.multibranch.SCMBinder.USE_HEAVYWEIGHT_CHECKOUT=true'

You would think this would be configurable per job, like it is in single pipeline job; not on a global scale via a Jenkins java argument.

 

This change was introduced with -JENKINS-33273">JENKINS-33273-.

 

Reason for this – I want to be able to do a PreBuildMerge action on the Jenkinsfile so the pipeline is up to date and tested with latest changes. Otherwise you are building/testing with an old pipeline which may fail after it's been accepted/merged.

Note: [If needed for testing] With latest plugins, Git PreBuildMerge extension is not valid with Multibranch Pipeline anymore. See Git-Plugin PR 513 https://github.com/jenkinsci/git-plugin/pull/513 to test with.

---
Originally reported by arty13, imported from: UI for SCMBinder.USE_HEAVYWEIGHT_CHECKOUT


  • status: Open
  • priority: Minor
  • component(s): workflow-multibranch-plugin
  • label(s): ui
  • resolution: Unresolved
  • votes: 1
  • watchers: 3
  • imported: 20251212-090250

Raw content of original issue

Currently the only way to do a heavy weight checkout is to set a system property for Jenkins java arguments. (viewable only from source code)
'-Dorg.jenkinsci.plugins.workflow.multibranch.SCMBinder.USE_HEAVYWEIGHT_CHECKOUT=true'

You would think this would be configurable per job, like it is in single pipeline job; not on a global scale via a Jenkins java argument.

 

This change was introduced with -JENKINS-33273-.

 

Reason for this – I want to be able to do a PreBuildMerge action on the Jenkinsfile so the pipeline is up to date and tested with latest changes. Otherwise you are building/testing with an old pipeline which may fail after it's been accepted/merged.

Note: [If needed for testing] With latest plugins, Git PreBuildMerge extension is not valid with Multibranch Pipeline anymore. See Git-Plugin PR 513 https://github.com/jenkinsci/git-plugin/pull/513 to test with.

environment

```
Jenkins Version: 2.60.2

workflow-multibranch-plugin: 2.16
```

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.