• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: workflow-multibranch-plugin
• Labels:

  • ui
• Environment:

  Jenkins Version: 2.60.2
  workflow-multibranch-plugin: 2.16

[JENKINS-45686] UI for SCMBinder.USE_HEAVYWEIGHT_CHECKOUT

Art V created issue - 2017-07-20 12:09

Art V made changes - 2017-07-20 12:10

Description

Original: 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.

New: 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.

Art V made changes - 2017-07-20 12:18

Description

Original: 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.

New: 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.

Jesse Glick made changes - 2017-08-03 15:10

Issue Type	Original: Bug [ 1 ]	New: Improvement [ 4 ]
Labels	Original: pipeline plugin	New: ui
Summary	Original: Unable to configure lightweight checkout for Multibranch Pipeline Job	New: UI for SCMBinder.USE_HEAVYWEIGHT_CHECKOUT

Collapse comment: Stephen Connolly added a comment - 2017-08-29 10:45

Stephen Connolly added a comment - 2017-08-29 10:45

Is this still relevant now there is 1.0 of the git-prebuildmerge-trait plugin?

Expand comment: Stephen Connolly added a comment - 2017-08-29 10:45

Stephen Connolly added a comment - 2017-08-29 10:45 Is this still relevant now there is 1.0 of the git-prebuildmerge-trait plugin?

Collapse comment: Art V added a comment - 2017-08-29 11:00

Art V added a comment - 2017-08-29 11:00

I believe this is still needed. Currently it's a global property and it should be per job property and with PreBuildMerge, it always needs to be enabled.

Expand comment: Art V added a comment - 2017-08-29 11:00

Art V added a comment - 2017-08-29 11:00 I believe this is still needed. Currently it's a global property and it should be per job property and with PreBuildMerge, it always needs to be enabled.