[JENKINS-68991] Controller path altered in mixed OS environment

[jenkins-infra-bot]

We have an issue when running pipelines in a mixed environment with a Linux controller and Windows agents.
When using a pipeline job that uses either the node or label parameters, if the node defined by the param value is a windows node then the pipeline checkout stage fails.

Checking out git https://xxxxxxxxx.git into /xxx/xxxx/workspace@​script to read resources/pipelines/playground/git-clone.groovy
The recommended git tool is: /usr/bin/git
using credential xxxxxxxxx
 > /usr/bin/git rev-parse --resolve-git-dir /xxx/xxxx/workspace@​script/.git # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url https://xxxxxxxx.git # timeout=10
Fetching upstream changes from https://xxxxxxxxxx.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (xxxxxxx)
 > /usr/bin/git fetch --tags --force --progress -- https://xxxxxxxx.git +refs/heads/*:refs/remotes/origin/* # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://xxxxxxxxxx.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:154)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:68)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:442)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --force --progress -- https://xxxxxxxxxxx.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: /xxx/xxxx/workspace@​script@​tmp/jenkins-gitclient-pass14582565555892846354.sh: line 3: cat: command not found
error: unable to read askpass response from '/xxx/xxxx/workspace@​script@​tmp/jenkins-gitclient-pass14582565555892846354.sh'
fatal: could not read Username for 'https://xxxxxxx.com': terminal prompts disabled

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2671)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2096)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:618)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
	... 8 more

The path of the controller is perfectly fine and any pipeline that doesn't use the node or label parameter types is correctly checked out from the same scm system with the same credentials.

It appears that the path on the controller is being overwritten by the path of the node resolved by the param.
When we change the label param to a simple string param and resolve the nodes explicitly in the pipeline everything works correctly.

Its not clear is this is an issue in the node and label parameter plugin or the gitscm plugin or a combination of both.

---

Originally reported by ffsetit, imported from: Controller path altered in mixed OS environment

• status: Open
• priority: Minor
• component(s): nodelabelparameter-plugin
• resolution: Unresolved
• votes: 0
• watchers: 4
• imported: 20251210-235911

Raw content of original issue

We have an issue when running pipelines in a mixed environment with a Linux controller and Windows agents.
When using a pipeline job that uses either the node or label parameters, if the node defined by the param value is a windows node then the pipeline checkout stage fails.


Checking out git https://xxxxxxxxx.git into /xxx/xxxx/workspace@script to read resources/pipelines/playground/git-clone.groovy
The recommended git tool is: /usr/bin/git
using credential xxxxxxxxx
 > /usr/bin/git rev-parse --resolve-git-dir /xxx/xxxx/workspace@script/.git # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url https://xxxxxxxx.git # timeout=10
Fetching upstream changes from https://xxxxxxxxxx.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (xxxxxxx)
 > /usr/bin/git fetch --tags --force --progress -- https://xxxxxxxx.git +refs/heads/*:refs/remotes/origin/* # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://xxxxxxxxxx.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:154)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:68)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:442)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --force --progress -- https://xxxxxxxxxxx.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: /xxx/xxxx/workspace@script@tmp/jenkins-gitclient-pass14582565555892846354.sh: line 3: cat: command not found
error: unable to read askpass response from '/xxx/xxxx/workspace@script@tmp/jenkins-gitclient-pass14582565555892846354.sh'
fatal: could not read Username for 'https://xxxxxxx.com': terminal prompts disabled

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2671)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2096)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:618)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
	... 8 more


The path of the controller is perfectly fine and any pipeline that doesn't use the node or label parameter types is correctly checked out from the same scm system with the same credentials.
It appears that the path on the controller is being overwritten by the path of the node resolved by the param.
When we change the label param to a simple string param and resolve the nodes explicitly in the pipeline everything works correctly.
Its not clear is this is an issue in the node and label parameter plugin or the gitscm plugin or a combination of both.

environment

Jenkins: 2.350<br/>
OS: Linux - 3.10.0-1160.59.1.el7.x86_64<br/>
---<br/>
Office-365-Connector:4.17.0<br/>
ace-editor:1.1<br/>
ansible:1.1<br/>
ansicolor:1.0.1<br/>
ant:475.vf34069fef73c<br/>
antisamy-markup-formatter:2.7<br/>
apache-httpcomponents-client-4-api:4.5.13-1.0<br/>
artifactory:3.16.2<br/>
authentication-tokens:1.4<br/>
authorize-project:1.4.0<br/>
badge:1.9.1<br/>
bitbucket:223.vd12f2bca5430<br/>
block-queued-job:0.2.0<br/>
blueocean:1.25.5<br/>
blueocean-autofavorite:1.2.5<br/>
blueocean-bitbucket-pipeline:1.25.5<br/>
blueocean-commons:1.25.5<br/>
blueocean-config:1.25.5<br/>
blueocean-core-js:1.25.5<br/>
blueocean-dashboard:1.25.5<br/>
blueocean-display-url:2.4.1<br/>
blueocean-events:1.25.5<br/>
blueocean-git-pipeline:1.25.5<br/>
blueocean-github-pipeline:1.25.5<br/>
blueocean-i18n:1.25.5<br/>
blueocean-jira:1.25.5<br/>
blueocean-jwt:1.25.5<br/>
blueocean-personalization:1.25.5<br/>
blueocean-pipeline-api-impl:1.25.5<br/>
blueocean-pipeline-editor:1.25.5<br/>
blueocean-pipeline-scm-api:1.25.5<br/>
blueocean-rest:1.25.5<br/>
blueocean-rest-impl:1.25.5<br/>
blueocean-web:1.25.5<br/>
bootstrap4-api:4.6.0-5<br/>
bootstrap5-api:5.1.3-7<br/>
bouncycastle-api:2.26<br/>
branch-api:2.1046.v0ca_37783ecc5<br/>
build-blocker-plugin:1.7.8<br/>
build-failure-analyzer:2.3.0<br/>
build-monitor-plugin:1.13+build.202205140447<br/>
build-timeout:1.21<br/>
build-token-root:1.9<br/>
build-user-vars-plugin:1.8<br/>
caffeine-api:2.9.3-65.v6a_47d0f4d1fe<br/>
checkmarx:2022.2.3<br/>
checks-api:1.7.4<br/>
claim:2.18.2<br/>
cloudbees-bitbucket-branch-source:773.v4b_9b_005b_562b_<br/>
cloudbees-folder:6.722.v8165b_a_cf25e9<br/>
command-launcher:84.v4a_97f2027398<br/>
conditional-buildstep:1.4.2<br/>
config-file-provider:3.10.0<br/>
configurationslicing:430.v966357576543<br/>
copyartifact:1.46.4<br/>
credentials:1129.vef26f5df883c<br/>
credentials-binding:523.vd859a_4b_122e6<br/>
custom-tools-plugin:0.8<br/>
dashboard-view:2.432.va_712ce35862d<br/>
database:148.v4a_ff2ca_608b_7<br/>
database-mysql:1.4<br/>
dependency-check-jenkins-plugin:5.1.2<br/>
dependency-track:4.1.1<br/>
discard-old-build:1.05<br/>
display-url-api:2.3.6<br/>
docker-commons:1.19<br/>
docker-java-api:3.1.5.2<br/>
docker-swarm:1.11<br/>
docker-workflow:1.28<br/>
durable-task:496.va67c6f9eefa7<br/>
echarts-api:5.3.2-2<br/>
email-ext:2.88<br/>
embeddable-build-status:2.0.3<br/>
envinject:2.866.v5c0403e3d4df<br/>
envinject-api:1.199.v3ce31253ed13<br/>
extended-choice-parameter:0.82<br/>
external-monitor-job:191.v363d0d1efdf8<br/>
favorite:2.4.1<br/>
file-operations:1.11<br/>
font-awesome-api:6.1.1-1<br/>
git:4.11.3<br/>
git-changelog:3.23<br/>
git-client:3.11.0<br/>
git-server:1.11<br/>
github:1.34.3<br/>
github-api:1.303-400.v35c2d8258028<br/>
github-branch-source:1637.vd833b_7ca_7654<br/>
google-metadata-plugin:0.3.1<br/>
google-oauth-plugin:1.0.6<br/>
google-storage-plugin:1.5.6<br/>
gradle:1.38<br/>
greenballs:1.15.1<br/>
groovy:2.4<br/>
groovy-postbuild:2.5<br/>
h2-api:1.4.199<br/>
handlebars:3.0.8<br/>
handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953<br/>
htmlpublisher:1.30<br/>
http_request:1.15<br/>
ivy:2.2<br/>
jackson2-api:2.13.3-285.vc03c0256d517<br/>
javadoc:217.v905b_86277a_2a_<br/>
javax-activation-api:1.2.0-3<br/>
javax-mail-api:1.6.2-6<br/>
jaxb:2.3.6-1<br/>
jdk-tool:1.5<br/>
jenkins-design-language:1.25.5<br/>
jira:3.7.1<br/>
jjwt-api:0.11.2-71.v2722b_b_06a_2a_f<br/>
job-dsl:1.79<br/>
jobConfigHistory:1146.v94c2521f9213<br/>
jquery:1.12.4-1<br/>
jquery-detached:1.2.1<br/>
jquery3-api:3.6.0-4<br/>
jsch:0.1.55.2<br/>
junit:1119.va_a_5e9068da_d7<br/>
kpp-management-plugin:1.0.0<br/>
label-linked-jobs:6.0.1<br/>
labelled-steps:1.0<br/>
ldap:2.10<br/>
leastload:3.0.0<br/>
lockable-resources:2.15<br/>
mailer:414.vcc4c33714601<br/>
mapdb-api:1.0.9.0<br/>
matrix-auth:3.1.2<br/>
matrix-project:771.v574584b_39e60<br/>
maven-plugin:3.19<br/>
mercurial:2.16.2<br/>
metrics:4.1.6.2<br/>
mina-sshd-api-common:2.8.0-21.v493b_6b_db_22c6<br/>
mina-sshd-api-core:2.8.0-21.v493b_6b_db_22c6<br/>
momentjs:1.1.1<br/>
monitoring:1.91.0<br/>
msbuild:1.30<br/>
mysql-api:8.0.16<br/>
nested-view:1.25<br/>
newrelic-deployment-notifier:1.8<br/>
nodejs:1.5.1<br/>
nodelabelparameter:1.10.3.1<br/>
oauth-credentials:0.5<br/>
okhttp-api:4.9.3-105.vb96869f8ac3a<br/>
pam-auth:1.8<br/>
parameterized-trigger:2.44<br/>
pipeline-build-step:2.18<br/>
pipeline-graph-analysis:195.v5812d95a_a_2f9<br/>
pipeline-groovy-lib:591.v3a_7f422b_d058<br/>
pipeline-input-step:448.v37cea_9a_10a_70<br/>
pipeline-maven:3.10.0<br/>
pipeline-milestone-step:101.vd572fef9d926<br/>
pipeline-model-api:2.2086.v12b_420f036e5<br/>
pipeline-model-definition:2.2086.v12b_420f036e5<br/>
pipeline-model-extensions:2.2086.v12b_420f036e5<br/>
pipeline-rest-api:2.24<br/>
pipeline-stage-step:293.v200037eefcd5<br/>
pipeline-stage-tags-metadata:2.2086.v12b_420f036e5<br/>
pipeline-stage-view:2.24<br/>
pipeline-utility-steps:2.12.1<br/>
plain-credentials:1.8<br/>
plugin-util-api:2.17.0<br/>
popper-api:1.16.1-3<br/>
popper2-api:2.11.5-2<br/>
powershell:1.7<br/>
preSCMbuildstep:0.3<br/>
promoted-builds:3.11<br/>
publish-over:0.22<br/>
publish-over-ftp:1.17<br/>
pubsub-light:1.16<br/>
pyenv-pipeline:2.1.2<br/>
resource-disposer:0.19<br/>
role-strategy:488.v0634ce149b_8c<br/>
run-condition:1.5<br/>
saml:2.298.vc7a_2b_3958628<br/>
scm-api:608.vfa_f971c5a_a_e9<br/>
scmskip:1.0.3<br/>
script-security:1175.v4b_d517d6db_f0<br/>
simple-theme-plugin:103.va_161d09c38c7<br/>
snakeyaml-api:1.30.1<br/>
sonar:2.14<br/>
sse-gateway:1.25<br/>
ssh-agent:295.v9ca_a_1c7cc3a_a_<br/>
ssh-credentials:277.v95c2fec1c047<br/>
ssh-slaves:1.814.vc82988f54b_10<br/>
sshd:3.237.v883d165a_c1d3<br/>
stashNotifier:1.28<br/>
strict-crumb-issuer:2.1.0<br/>
structs:318.va_f3ccb_729b_71<br/>
test-results-aggregator:1.2.9<br/>
thinBackup:1.10<br/>
timestamper:1.17<br/>
token-macro:293.v283932a_0a_b_49<br/>
trilead-api:1.57.v6e90e07157e1<br/>
uno-choice:2.6.2<br/>
variant:1.4<br/>
view-job-filters:2.3<br/>
windows-slaves:1.8.1<br/>
workflow-aggregator:581.v0c46fa_697ffd<br/>
workflow-api:1153.vb_912c0e47fb_a_<br/>
workflow-basic-steps:948.v2c72a_091b_b_68<br/>
workflow-cps:2706.v71dd22b_c5a_a_2<br/>
workflow-cps-global-lib:588.v576c103a_ff86<br/>
workflow-durable-task-step:1139.v252a_e12e8463<br/>
workflow-job:1182.v60a_e6279b_579<br/>
workflow-multibranch:716.vc692a_e52371b_<br/>
workflow-scm-step:400.v6b_89a_1317c9a_<br/>
workflow-step-api:625.vd896b_f445a_f8<br/>
workflow-support:820.vd1a_6cc65ef33<br/>
ws-cleanup:0.42<br/>
openjdk version &quot;11.0.14.1&quot; 2022-02-08 LTS<br/>
OpenJDK Runtime Environment 18.9 (build 11.0.14.1+1-LTS)<br/>
OpenJDK 64-Bit Server VM 18.9 (build 11.0.14.1+1-LTS, mixed mode, sharing)

1 attachment

• Config-history-label_string.png

  

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I can't duplicate the issue.  Steps that I took while trying to duplicate the issue included:
  
  
  	
  Create a Pipeline job on my Linux controller that defines a label parameter AGENT_LABEL using the node label parameter plugin
  	
  Add the declarative Pipeline script as follows:
  
  pipeline {
      agent {
          label env.AGENT_LABEL
      }
      stages {
          stage('Checkout') {
              steps {
                  // Get some files from a Bitbucket repository
                  checkout([$class: 'GitSCM', branches: [[name: 'master']], 
                      userRemoteConfigs: [[credentialsId: 'jenkins-bugs-repo-scan-password-bitbucket', 
                                           url: 'https://markewaite@bitbucket.org/markewaite/tasks.git']]])
              }
          }
      }
  }
  
  
  	
  Run the Pipeline job, enter the 'windows' label for the job and confirm that the checkout is correct on the Windows agent.
  
  That is a rather uncommon way to define parameters to a Pipeline job, since it places the definition of the parameters outside the Pipeline script.
  I wonder if you may have defined the git tool in the global tool configuration as /usr/bin/git instead of defining it with the recommended value of git.  The /usr/bin/git value is only valid on Linux platforms and some other Unix platforms.  It is not valid on FreeBSD or OpenBSD or even on many Windows computers.
  Please provide more details so that others can duplicate the issue.
  The job definition I used for my test looks like this
  
  <?xml version='1.1' encoding='UTF-8'?>
  <flow-definition plugin="workflow-job@1207.ve6191ff089f8">
    <actions>
      <org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobAction plugin="pipeline-model-definition@2.2114.v2654ca_721309"/>
      <org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction plugin="pipeline-model-definition@2.2114.v2654ca_721309">
        <jobProperties/>
        <triggers/>
        <parameters/>
        <options/>
      </org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction>
    </actions>
    <description>[JENKINS-68991](https://issues.jenkins.io/browse/JENKINS-68991) reports that checkout fails on a Windows agent with Linux controller using a node or label parameter</description>
    <keepDependencies>false</keepDependencies>
    <properties>
      <hudson.model.ParametersDefinitionProperty>
        <parameterDefinitions>
          <org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterDefinition plugin="nodelabelparameter@1.11.0">
            <name>AGENT_LABEL</name>
            <description>Label of agent that will run the job</description>
            <defaultValue>windows</defaultValue>
            <allNodesMatchingLabel>false</allNodesMatchingLabel>
            <triggerIfResult>allCases</triggerIfResult>
            <nodeEligibility class="org.jvnet.jenkins.plugins.nodelabelparameter.node.AllNodeEligibility"/>
          </org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterDefinition>
        </parameterDefinitions>
      </hudson.model.ParametersDefinitionProperty>
    </properties>
    <definition class="org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition" plugin="workflow-cps@2746.v0da_83a_332669">
      <script>pipeline {
      agent {
          label env.AGENT_LABEL
      }
      stages {
          stage(&apos;Checkout&apos;) {
              steps {
                  // Get some files from a Bitbucket repository
                  checkout([$class: &apos;GitSCM&apos;, branches: [[name: &apos;master&apos;]],
                      userRemoteConfigs: [[credentialsId: &apos;jenkins-bugs-repo-scan-password-bitbucket&apos;,
                                           url: &apos;https://markewaite@bitbucket.org/markewaite/tasks.git&apos;]]])
              }
          }
      }
  }
  </script>
      <sandbox>true</sandbox>
    </definition>
    <triggers/>
    <disabled>false</disabled>
  </flow-definition>
  
  
  

I can't duplicate the issue. Steps that I took while trying to duplicate the issue included:

1. Create a Pipeline job on my Linux controller that defines a label parameter AGENT_LABEL using the node label parameter plugin
2. Add the declarative Pipeline script as follows:

   pipeline {
       agent {
   label env.AGENT_LABEL
       }
       stages {
   stage('Checkout') {
       steps {
   // Get some files from a Bitbucket repository
   checkout([$class: 'GitSCM', branches: [[name: 'master']], 
       userRemoteConfigs: [[credentialsId: 'jenkins-bugs-repo-scan-password-bitbucket', 
    url: 'https://markewaite@​bitbucket.org/markewaite/tasks.git']]])
       }
   }
       }
   }
   
   ```</li>
   	<li>Run the Pipeline job, enter the 'windows' label for the job and confirm that the checkout is correct on the Windows agent.</li>
   </ol>
   
   
   <p>That is a rather uncommon way to define parameters to a Pipeline job, since it places the definition of the parameters outside the Pipeline script.</p>
   
   <p>I wonder if you may have defined the <tt>git tool</tt> in the global tool configuration as <tt>/usr/bin/git</tt> instead of defining it with the recommended value of <tt>git</tt>.  The <tt>/usr/bin/git</tt> value is only valid on Linux platforms and some other Unix platforms.  It is not valid on FreeBSD or OpenBSD or even on many Windows computers.</p>
   
   <p>Please provide more details so that others can duplicate the issue.</p>
   
   <p>The job definition I used for my test looks like this</p>
   
   
   
   

   [JENKINS-68991](https://issue-redirect.jenkins.io/issue/68991) reports that checkout fails on a Windows agent with Linux controller using a node or label parameter false AGENT_LABEL Label of agent that will run the job windows false allCases <script>pipeline { agent { label env.AGENT_LABEL } stages { stage('Checkout') { steps { // Get some files from a Bitbucket repository checkout([$class: 'GitSCM', branches: [[name: 'master']], userRemoteConfigs: [[credentialsId: 'jenkins-bugs-repo-scan-password-bitbucket', url: 'https://markewaite@​bitbucket.org/markewaite/tasks.git']]]) } } } } </script> true false

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I'm unable to duplicate the problem as reporting.  If the submitter provides more information, they can reopen the issue.
  

I'm unable to duplicate the problem as reporting. If the submitter provides more information, they can reopen the issue.

[jenkins-infra-bot]

ffsetit:

• Original comment link
• Raw content of original comment:

  Here is some additional information for replication.
  
  The test job we are using is 
  
  
  This XML file does not appear to have any style information associated with it. The document tree is shown below.
  <flow-definition plugin="workflow-job@1182.v60a_e6279b_579">
  <actions>
  <org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobAction plugin="pipeline-model-definition@2.2086.v12b_420f036e5"/>
  <org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction plugin="pipeline-model-definition@2.2086.v12b_420f036e5">
  <jobProperties>
  <string>jenkins.model.BuildDiscarderProperty</string>
  </jobProperties>
  <triggers/>
  <parameters/>
  <options>
  <string>skipDefaultCheckout</string>
  </options>
  </org.jenkinsci.plugins.pipeline.modeldefinition.actions.DeclarativeJobPropertyTrackerAction>
  </actions>
  <description/>
  <keepDependencies>false</keepDependencies>
  <properties>
  <hudson.plugins.jira.JiraProjectProperty plugin="jira@3.7.1"/>
  <hudson.plugins.buildblocker.BuildBlockerProperty plugin="build-blocker-plugin@1.7.8">
  <useBuildBlocker>false</useBuildBlocker>
  <blockLevel>GLOBAL</blockLevel>
  <scanQueueFor>DISABLED</scanQueueFor>
  <blockingJobs/>
  </hudson.plugins.buildblocker.BuildBlockerProperty>
  <com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty plugin="build-failure-analyzer@2.3.0">
  <doNotScan>false</doNotScan>
  </com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty>
  <org.bstick12.jenkinsci.plugins.leastload.LeastLoadDisabledProperty plugin="leastload@3.0.0">
  <leastLoadDisabled>false</leastLoadDisabled>
  </org.bstick12.jenkinsci.plugins.leastload.LeastLoadDisabledProperty>
  <hudson.model.ParametersDefinitionProperty>
  <parameterDefinitions>
  <org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterDefinition plugin="nodelabelparameter@1.10.3.1">
  <name>NODE</name>
  <defaultValue>Build_Linux</defaultValue>
  <allNodesMatchingLabel>false</allNodesMatchingLabel>
  <triggerIfResult>allCases</triggerIfResult>
  <nodeEligibility class="org.jvnet.jenkins.plugins.nodelabelparameter.node.AllNodeEligibility"/>
  </org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterDefinition>
  </parameterDefinitions>
  </hudson.model.ParametersDefinitionProperty>
  <EnvInjectJobProperty plugin="envinject@2.866.v5c0403e3d4df">
  <info>
  <secureGroovyScript plugin="script-security@1175.v4b_d517d6db_f0">
  <script/>
  <sandbox>false</sandbox>
  </secureGroovyScript>
  <loadFilesFromMaster>false</loadFilesFromMaster>
  </info>
  <on>true</on>
  <keepJenkinsSystemVariables>true</keepJenkinsSystemVariables>
  <keepBuildVariables>true</keepBuildVariables>
  <overrideBuildParameters>false</overrideBuildParameters>
  </EnvInjectJobProperty>
  <org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty>
  <triggers/>
  </org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty>
  <jenkins.model.BuildDiscarderProperty>
  <strategy class="hudson.tasks.LogRotator">
  <daysToKeep>-1</daysToKeep>
  <numToKeep>100</numToKeep>
  <artifactDaysToKeep>-1</artifactDaysToKeep>
  <artifactNumToKeep>-1</artifactNumToKeep>
  </strategy>
  </jenkins.model.BuildDiscarderProperty>
  </properties>
  <definition class="org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="workflow-cps@2706.v71dd22b_c5a_a_2">
  <scm class="hudson.plugins.git.GitSCM" plugin="git@4.11.3">
  <configVersion>2</configVersion>
  <userRemoteConfigs>
  <hudson.plugins.git.UserRemoteConfig>
  <url>https://wfrbitbucket.int.kronos.com/scm/devops/jenkins-pipeline.git</url>
  <credentialsId>svc_bitbucket-server_ro_user</credentialsId>
  </hudson.plugins.git.UserRemoteConfig>
  </userRemoteConfigs>
  <branches>
  <hudson.plugins.git.BranchSpec>
  <name>develop</name>
  </hudson.plugins.git.BranchSpec>
  </branches>
  <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
  <gitTool>Default</gitTool>
  <submoduleCfg class="empty-list"/>
  <extensions/>
  </scm>
  <scriptPath>resources/pipelines/playground/downstream-job-stub.groovy</scriptPath>
  <lightweight>false</lightweight>
  </definition>
  <triggers/>
  <disabled>false</disabled>
  </flow-definition>
  
  
  The pipeline is
  
  library identifier: "jenkins-pipeline@${scm.branches[0]}"
  // Environment
  
  NODE = env.NODE ?: 'master' // 'Build_Coordinator'
  
  
  
  pipeline {
  
  agent {
  
  node {
  
  label NODE
  
  }
  
  }
  
  options {
  
  buildDiscarder(logRotator(numToKeepStr: '100'))
  
  skipDefaultCheckout(true)
  
  timestamps()
  
  timeout(time: 6, unit: 'HOURS')
  
  }
  stages {
      stage(<span class="code-quote">'Echo'</span>) {
          steps {
              script {
                  echoPipelineParams(<span class="code-keyword">this</span>)
              }
          }
      }
  }
  
  }
  
  
  
  The global tool definition for git "Default" is indeed /usr/bin/git, however this isn't the issue as its finding git correctly.
  First run using a label that resolves to a linux agent
  
  Started by user Peter Barnes
  Running as Peter Barnes
  Checking out git https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
  The recommended git tool is: /usr/bin/git
  using credential svc_bitbucket-server_ro_user
  Cloning the remote Git repository
  Cloning repository https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git init /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf # timeout=10
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
   > /usr/bin/git fetch --tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
   > /usr/bin/git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
   > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
  Avoid second fetch
   > /usr/bin/git rev-parse origin/develop^{commit} # timeout=10
  Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (origin/develop)
   > /usr/bin/git config core.sparsecheckout # timeout=10
   > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
  Commit message: "Fixed terraform version error message"
  First time build. Skipping changelog.
  [Pipeline] Start of Pipeline
  [Pipeline] library
  Loading library jenkins-pipeline@develop
  Attempting to resolve develop from remote references...
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Git user to run builds
   > /usr/bin/git ls-remote -h -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Found match: refs/heads/develop revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c
  The recommended git tool is: /usr/bin/git
  using credential Build_Master
  Cloning the remote Git repository
  Cloning with configured refspecs honoured and without tags
  Cloning repository https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git init /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@libs/8223231c7e88e615fc872707238792ff5c49b59664553872ad97ac9171dfa4d3 # timeout=10
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Git user to run builds
   > /usr/bin/git fetch --no-tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
   > /usr/bin/git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
   > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
  Avoid second fetch
  Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (develop)
   > /usr/bin/git config core.sparsecheckout # timeout=10
   > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
  Commit message: "Fixed terraform version error message"
  [Pipeline] node
  Running on <<A-LINUX-AGENT>> in /home/jenkins/workspace/PLAYGROUND/project-clone.test
  [Pipeline] {
  [Pipeline] timestamps
  [Pipeline] {
  [Pipeline] timeout
  11:31:15  Timeout set to expire in 6 hr 0 min
  [Pipeline] {
  [Pipeline] stage
  [Pipeline] { (Echo)
  [Pipeline] script
  [Pipeline] {
  [Pipeline] echo
  11:31:15  ========== Pipeline Parameters ==========
  11:31:15  NODE: Build_Linux
  [Pipeline] }
  [Pipeline] // script
  [Pipeline] }
  [Pipeline] // stage
  [Pipeline] }
  [Pipeline] // timeout
  [Pipeline] }
  [Pipeline] // timestamps
  [Pipeline] }
  [Pipeline] // node
  [Pipeline] End of Pipeline
  Finished: SUCCESS
  
  
  Second run that resolves to a Windows agent
  
  Started by user Peter Barnes
  Running as Peter Barnes
  Checking out git https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
  The recommended git tool is: /usr/bin/git
  using credential svc_bitbucket-server_ro_user
   > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
  Fetching changes from the remote Git repository
   > /usr/bin/git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
   > /usr/bin/git fetch --tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
  ERROR: Error fetching remote repo 'origin'
  hudson.plugins.git.GitException: Failed to fetch from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
  	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1003)
  	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1244)
  	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
  	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
  	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:159)
  	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
  	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)
  	at hudson.model.ResourceController.execute(ResourceController.java:101)
  	at hudson.model.Executor.run(Executor.java:442)
  Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
  stdout: 
  stderr: /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf@tmp/jenkins-gitclient-pass5279391599576956511.sh: line 3: cat: command not found
  
  
  

Here is some additional information for replication.

The test job we are using is

This XML file does not appear to have any style information associated with it. The document tree is shown below.
"workflow-job@​1182.v60a_e6279b_579">

"pipeline-model-definition@​2.2086.v12b_420f036e5"/>
"pipeline-model-definition@​2.2086.v12b_420f036e5">

jenkins.model.BuildDiscarderProperty




skipDefaultCheckout




false

"jira@​3.7.1"/>
"build-blocker-plugin@​1.7.8">
false
GLOBAL
DISABLED


"build-failure-analyzer@​2.3.0">
false

"leastload@​3.0.0">
false



"nodelabelparameter@​1.10.3.1">
NODE
Build_Linux
false
allCases
"org.jvnet.jenkins.plugins.nodelabelparameter.node.AllNodeEligibility"/>



"envinject@​2.866.v5c0403e3d4df">

"script-security@​1175.v4b_d517d6db_f0">
<script/>
false

false

true
true
true
false





"hudson.tasks.LogRotator">
-1
100
-1
-1



"org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="workflow-cps@​2706.v71dd22b_c5a_a_2">
"hudson.plugins.git.GitSCM" plugin="git@​4.11.3">
2


https://wfrbitbucket.int.kronos.com/scm/devops/jenkins-pipeline.git
svc_bitbucket-server_ro_user




develop


false
Default
"empty-list"/>


resources/pipelines/playground/downstream-job-stub.groovy
false


false

The pipeline is

library identifier: "jenkins-pipeline@${scm.branches[0]}"

// Environment
NODE = env.NODE ?: 'master' // 'Build_Coordinator'

pipeline {
    agent {
node {
    label NODE
}
    }
    options {
buildDiscarder(logRotator(numToKeepStr: '100'))
skipDefaultCheckout(true)
timestamps()
timeout(time: 6, unit: 'HOURS')
    }

    stages {
stage('Echo') {
    steps {
script {
    echoPipelineParams(this)
}
    }
}
    }
}

The global tool definition for git "Default" is indeed /usr/bin/git, however this isn't the issue as its finding git correctly.

First run using a label that resolves to a linux agent

Started by user Peter Barnes
Running as Peter Barnes
Checking out git https://..com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
The recommended git tool is: /usr/bin/git
using credential svc_bitbucket-server_ro_user
Cloning the remote Git repository
Cloning repository https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git init /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf # timeout=10
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
 > /usr/bin/git fetch --tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
 > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 > /usr/bin/git rev-parse origin/develop^{commit} # timeout=10
Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (origin/develop)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
Commit message: "Fixed terraform version error message"
First time build. Skipping changelog.
[Pipeline] Start of Pipeline
[Pipeline] library
Loading library jenkins-pipeline@​develop
Attempting to resolve develop from remote references...
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Git user to run builds
 > /usr/bin/git ls-remote -h -- https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Found match: refs/heads/develop revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c
The recommended git tool is: /usr/bin/git
using credential Build_Master
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git init /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​libs/8223231c7e88e615fc872707238792ff5c49b59664553872ad97ac9171dfa4d3 # timeout=10
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Git user to run builds
 > /usr/bin/git fetch --no-tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
 > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (develop)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
Commit message: "Fixed terraform version error message"
[Pipeline] node
Running on <> in /home/jenkins/workspace/PLAYGROUND/project-clone.test
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] timeout
11:31:15  Timeout set to expire in 6 hr 0 min
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Echo)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
11:31:15  ========== Pipeline Parameters ==========
11:31:15  NODE: Build_Linux
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

Second run that resolves to a Windows agent

Started by user Peter Barnes
Running as Peter Barnes
Checking out git https://..com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
The recommended git tool is: /usr/bin/git
using credential svc_bitbucket-server_ro_user
 > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
 > /usr/bin/git fetch --tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://..com/scm/devops/jenkins-pipeline.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1003)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1244)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:159)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:442)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf@​tmp/jenkins-gitclient-pass5279391599576956511.sh: line 3: cat: command not found

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  however this isn't the issue as its finding git correctly
  
  It is finding the git executable at /usr/bin/git but then I think it is assuming that it will find a cat command to use in a shell script that provides the username / password for HTTP authentication.  It can't find cat because it is running on Windows.  The plugin uses a bat file on Windows to provide the authentication information for repositories accessed by HTTPS.  It should not be mentioning cat on a Windows agent at all.
  
  Did you try my recommendation of switching the Default git configuration from /usr/bin/git to git?
  
  Another approach would be to switch from HTTPS to ssh for authentication for the git repository (if your installation supports ssh authentication of the repository).
  
  Yet another approach for repositories less than 50 MB is to enable JGit and switch the implementation to use JGit instead of command line git.  JGit performs the git operations inside the Java process instead of starting a separate git program.  In the Jenkins use case, we found that JGit is consistently faster than command line git for repositories of 5 MB or less.  It was consistently slower than command line git for repositories of 50 MB or more.
  

however this isn't the issue as its finding git correctly

It is finding the git executable at /usr/bin/git but then I think it is assuming that it will find a cat command to use in a shell script that provides the username / password for HTTP authentication. It can't find cat because it is running on Windows. The plugin uses a bat file on Windows to provide the authentication information for repositories accessed by HTTPS. It should not be mentioning cat on a Windows agent at all.

Did you try my recommendation of switching the Default git configuration from /usr/bin/git to git?

Another approach would be to switch from HTTPS to ssh for authentication for the git repository (if your installation supports ssh authentication of the repository).

Yet another approach for repositories less than 50 MB is to enable JGit and switch the implementation to use JGit instead of command line git. JGit performs the git operations inside the Java process instead of starting a separate git program. In the Jenkins use case, we found that JGit is consistently faster than command line git for repositories of 5 MB or less. It was consistently slower than command line git for repositories of 50 MB or more.

[jenkins-infra-bot]

ffsetit:

• Original comment link
• Raw content of original comment:

  How do we explain this behaviour then. If I change the parameter type Label > String the build works correctly
  
  
  Checking out git https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
  The recommended git tool is: /usr/bin/git
  using credential svc_bitbucket-server_ro_user
   > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
  Fetching changes from the remote Git repository
   > /usr/bin/git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
   > /usr/bin/git fetch --tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
   > /usr/bin/git rev-parse origin/develop^{commit} # timeout=10
  Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (origin/develop)
   > /usr/bin/git config core.sparsecheckout # timeout=10
   > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
  Commit message: "Fixed terraform version error message"
   > /usr/bin/git rev-list --no-walk 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
  [Pipeline] Start of Pipeline
  [Pipeline] library
  Loading library jenkins-pipeline@develop
  Attempting to resolve develop from remote references...
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Git user to run builds
   > /usr/bin/git ls-remote -h -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Found match: refs/heads/develop revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c
  The recommended git tool is: /usr/bin/git
  using credential Build_Master
   > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@libs/8223231c7e88e615fc872707238792ff5c49b59664553872ad97ac9171dfa4d3/.git # timeout=10
  Fetching changes from the remote Git repository
   > /usr/bin/git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Fetching without tags
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > /usr/bin/git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Git user to run builds
   > /usr/bin/git fetch --no-tags --force --progress -- https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
  Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (develop)
   > /usr/bin/git config core.sparsecheckout # timeout=10
   > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
  Commit message: "Fixed terraform version error message"
  [Pipeline] node
  Running on wfr01-i01-bs51 in D:\jenkins_slave\workspace\PLAYGROUND\project-clone.test
  [Pipeline] {
  [Pipeline] timestamps
  [Pipeline] {
  [Pipeline] timeout
  14:35:53  Timeout set to expire in 6 hr 0 min
  [Pipeline] {
  [Pipeline] stage
  [Pipeline] { (Echo)
  [Pipeline] script
  [Pipeline] {
  [Pipeline] echo
  14:35:53  ========== Pipeline Parameters ==========
  14:35:53  NODE: Build_Win
  [Pipeline] }
  [Pipeline] // script
  [Pipeline] }
  [Pipeline] // stage
  [Pipeline] }
  [Pipeline] // timeout
  [Pipeline] }
  [Pipeline] // timestamps
  [Pipeline] }
  [Pipeline] // node
  [Pipeline] End of Pipeline
  Finished: SUCCESS
  
  
    
  

How do we explain this behaviour then. If I change the parameter type Label > String the build works correctly

Checking out git https://..com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
The recommended git tool is: /usr/bin/git
using credential svc_bitbucket-server_ro_user
 > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
 > /usr/bin/git fetch --tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git rev-parse origin/develop^{commit} # timeout=10
Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (origin/develop)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
Commit message: "Fixed terraform version error message"
 > /usr/bin/git rev-list --no-walk 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
[Pipeline] Start of Pipeline
[Pipeline] library
Loading library jenkins-pipeline@​develop
Attempting to resolve develop from remote references...
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Git user to run builds
 > /usr/bin/git ls-remote -h -- https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Found match: refs/heads/develop revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c
The recommended git tool is: /usr/bin/git
using credential Build_Master
 > /usr/bin/git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​libs/8223231c7e88e615fc872707238792ff5c49b59664553872ad97ac9171dfa4d3/.git # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Fetching without tags
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > /usr/bin/git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Git user to run builds
 > /usr/bin/git fetch --no-tags --force --progress -- https://..com/scm/devops/jenkins-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Checking out Revision 9ecbc7eaa7b1f722f0e096e3989731ee0983340c (develop)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 9ecbc7eaa7b1f722f0e096e3989731ee0983340c # timeout=10
Commit message: "Fixed terraform version error message"
[Pipeline] node
Running on wfr01-i01-bs51 in D:\jenkins_slave\workspace\PLAYGROUND\project-clone.test
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] timeout
14:35:53  Timeout set to expire in 6 hr 0 min
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Echo)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
14:35:53  ========== Pipeline Parameters ==========
14:35:53  NODE: Build_Win
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I don't have an explanation for the difference in behavior.  I could make guesses at the difference in behavior, but I don't think that those guesses will help you resolve the issue you are seeing.
  

I don't have an explanation for the difference in behavior. I could make guesses at the difference in behavior, but I don't think that those guesses will help you resolve the issue you are seeing.

[jenkins-infra-bot]

ffsetit:

• Original comment link
• Raw content of original comment:

  Correct me if i'm wrong, but its performing the initial pipeline checkout on the controller and not the agent, its only once the initial checkout is complete that execution switches to the defined agent. 
  
  If this is the case then the issue isn't with the agent as its not even getting that far as the checkout on the controller is failing
  

Correct me if i'm wrong, but its performing the initial pipeline checkout on the controller and not the agent, its only once the initial checkout is complete that execution switches to the defined agent.

If this is the case then the issue isn't with the agent as its not even getting that far as the checkout on the controller is failing

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I've offered my suggestions.
  
  With my installation, I always set the git default tool to be git so that it is found through the PATH on all platforms.  When I change that configuration to specify /usr/bin/git and then try to run a Windows based Pipeline job, it fails with the message:
  
  
  Caused: java.io.IOException: Cannot run program "nohup" (in directory "C:\J\XO\workspace\line-Checks_bin-bitbucket_master"): CreateProcess error=2, The system cannot find the file specified
  
  
  I believe that is a similar case to what you are reporting.  I've suggested that you should change your git tool configuration.  You get to choose if you try that or not.
  

I've offered my suggestions.

With my installation, I always set the git default tool to be git so that it is found through the PATH on all platforms. When I change that configuration to specify /usr/bin/git and then try to run a Windows based Pipeline job, it fails with the message:

Caused: java.io.IOException: Cannot run program "nohup" (in directory "C:\J\XO\workspace\line-Checks_bin-bitbucket_master"): CreateProcess error=2, The system cannot find the file specified

I believe that is a similar case to what you are reporting. I've suggested that you should change your git tool configuration. You get to choose if you try that or not.

[jenkins-infra-bot]

ffsetit:

• Original comment link
• Raw content of original comment:

  I added a new git tool "git" with the command line set to just git without the path and set this test job to use it
  
  
  Checking out git https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
  The recommended git tool is: git
  using credential svc_bitbucket-server_ro_user
   > git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
  Fetching changes from the remote Git repository
   > git config remote.origin.url https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git # timeout=10
  Fetching upstream changes from https://<sub-domain>.<domain>.com/scm/devops/jenkins-pipeline.git
   > git --version # timeout=10
   > git --version # 'git version 2.24.4'
  using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
  ....
  stderr: /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf@tmp/jenkins-gitclient-pass14792681976646570415.sh: line 3: cat: command not found
  
  
  
  Unfortunately it doesn't change annything
  

I added a new git tool "git" with the command line set to just git without the path and set this test job to use it

Checking out git https://..com/scm/devops/jenkins-pipeline.git into /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf to read resources/pipelines/playground/downstream-job-stub.groovy
The recommended git tool is: git
using credential svc_bitbucket-server_ro_user
 > git rev-parse --resolve-git-dir /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://..com/scm/devops/jenkins-pipeline.git # timeout=10
Fetching upstream changes from https://..com/scm/devops/jenkins-pipeline.git
 > git --version # timeout=10
 > git --version # 'git version 2.24.4'
using GIT_ASKPASS to set credentials Bitbucket Server (Build_master)
....
stderr: /apps/jenkins/jobs/PLAYGROUND/jobs/project-clone.test/workspace@​script/3658c71abf61f0dc7a11eb78fccc9c1b8cb716fe1f7f4bf454a7e6f5036b31bf@​tmp/jenkins-gitclient-pass14792681976646570415.sh: line 3: cat: command not found

Unfortunately it doesn't change annything

[jenkins-infra-bot]

bphinz:

• Original comment link
• Raw content of original comment:

  I'm seeing the exact same behavior.  My controller is linux and I have both Windows and Linux agents. If I attempt to use the Node & Label parameter plugin in a pipeline job and select a Windows node, then the pipeline checkout fails (on the master) because the PATH env var has been altered and it cannot find /usr/bin/ssh.  The error does NOT occur if:
  
  (1) I select a Linux node with the plugin
  (2) I don't use the plugin in a job
  
  In my case, I'm really only using it to select a node name and save it in a variable, so I can work around it by using a static list of nodes in a drop-down select, but I've spent weeks chasing this before I realized that there was a correlation with the plugin.
  

I'm seeing the exact same behavior.  My controller is linux and I have both Windows and Linux agents. If I attempt to use the Node & Label parameter plugin in a pipeline job and select a Windows node, then the pipeline checkout fails (on the master) because the PATH env var has been altered and it cannot find /usr/bin/ssh.  The error does NOT occur if:

(1) I select a Linux node with the plugin
(2) I don't use the plugin in a job

In my case, I'm really only using it to select a node name and save it in a variable, so I can work around it by using a static list of nodes in a drop-down select, but I've spent weeks chasing this before I realized that there was a correlation with the plugin.

[jenkins-infra-bot]

vorting:

• Original comment link
• Raw content of original comment:

  Greetings. I have the same issue. But when I run the pipeline on its own, it works properly. And when I add it to the Multijob project it works until project reaches this job
  Dev_Copy_Config_Pipeline and then an error appears. I changed git-URL for security reasons
  
  Started by upstream project "Dev-Full\_Clone" build number 112
  originally caused by:
  Started by user Jenkins Admin User
  Lightweight checkout support not available, falling back to full checkout.
  Checking out git git@github.com:remote/repo.git into /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@script to read Jenkinsfile
  The recommended git tool is: git
  using credential some_credentials
  > git rev-parse --resolve-git-dir /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@script/.git # timeout=10
  > Fetching changes from the remote Git repository
  > git config remote.origin.url git@github.com:remote/repo.git # timeout=10
  > Fetching upstream changes from git@github.com:remote/repo.git.git
  > git --version # timeout=10
  > git --version # 'git version 2.30.2'
  > using GIT\_SSH to set credentials SSH Key for GitHub
  > git fetch --tags --force --progress -- git@github.com:remote/repo.git +refs/heads/_:refs/remotes/origin/_ # timeout=10
  > ERROR: Error fetching remote repo 'origin'
  > hudson.plugins.git.GitException: Failed to fetch from git@github.com:remote/repo.git
  > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001)
  > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242)
  > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)
  > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
  > at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:154)
  > at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:68)
  > at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:310)
  > at hudson.model.ResourceController.execute(ResourceController.java:99)
  > at hudson.model.Executor.run(Executor.java:431)
  > Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- git@github.com:remote/repo.git +refs/heads/_:refs/remotes/origin/_" returned status code 128:
  > stdout:
  > stderr: /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@script@tmp/jenkins-gitclient-pass735120008306329194.sh: 2: cat: not found
  > git@github.com: Permission denied (publickey).
  > fatal: Could not read from remote repository.
  Please make sure you have the correct access rights
  and the repository exists.
  ```
  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2681)
  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2102)
  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:86)
  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:624)
  at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
  ... 8 more
  ```
  ERROR: Error fetching remote repo 'origin'
  ERROR: Maximum checkout retry attempts reached, aborting
  Finished: FAILURE
  
  
  We don't have Windows agents, we have only CentOS/Ubuntu ssh-agents. 
  We use the Jenkins version of 2.303.3 running in Docker-container
   
  

Greetings. I have the same issue. But when I run the pipeline on its own, it works properly. And when I add it to the Multijob project it works until project reaches this job
Dev_Copy_Config_Pipeline and then an error appears. I changed git-URL for security reasons

Started by upstream project "Dev-Full\_Clone" build number 112
originally caused by:
Started by user Jenkins Admin User
Lightweight checkout support not available, falling back to full checkout.
Checking out git git@​github.com:remote/repo.git into /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@​script to read Jenkinsfile
The recommended git tool is: git
using credential some_credentials
> git rev-parse --resolve-git-dir /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@​script/.git # timeout=10
> Fetching changes from the remote Git repository
> git config remote.origin.url git@​github.com:remote/repo.git # timeout=10
> Fetching upstream changes from git@​github.com:remote/repo.git.git
> git --version # timeout=10
> git --version # 'git version 2.30.2'
> using GIT\_SSH to set credentials SSH Key for GitHub
> git fetch --tags --force --progress -- git@​github.com:remote/repo.git +refs/heads/_:refs/remotes/origin/_ # timeout=10
> ERROR: Error fetching remote repo 'origin'
> hudson.plugins.git.GitException: Failed to fetch from git@​github.com:remote/repo.git
> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001)
> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)
> at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)
> at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:154)
> at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:68)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:310)
> at hudson.model.ResourceController.execute(ResourceController.java:99)
> at hudson.model.Executor.run(Executor.java:431)
> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- git@​github.com:remote/repo.git +refs/heads/_:refs/remotes/origin/_" returned status code 128:
> stdout:
> stderr: /var/jenkins\_home/workspace/Dev\_Copy\_Config\_Pipeline@​script@​tmp/jenkins-gitclient-pass735120008306329194.sh: 2: cat: not found
> git@​github.com: Permission denied (publickey).
> fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
```
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2681)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2102)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:86)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:624)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
... 8 more
```
ERROR: Error fetching remote repo 'origin'
ERROR: Maximum checkout retry attempts reached, aborting
Finished: FAILURE

We don't have Windows agents, we have only CentOS/Ubuntu ssh-agents. 
We use the Jenkins version of 2.303.3 running in Docker-container

 

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  vorting the Multijob plugin is deprecated.  The plugin page says:
  
  This plugin has been marked as deprecated. In general, this means that this plugin is either obsolete, no longer being developed, or may no longer work.
  
  I don't test the Multijob plugin.  I think you should do your best to replace the deprecated Multijob plugin with PIpeline.
  

vorting the Multijob plugin is deprecated. The plugin page says:

This plugin has been marked as deprecated. In general, this means that this plugin is either obsolete, no longer being developed, or may no longer work.

I don't test the Multijob plugin. I think you should do your best to replace the deprecated Multijob plugin with PIpeline.

[jenkins-infra-bot]

vorting:

• Original comment link
• Raw content of original comment:

  Thank you for the response. I am going to work without Multijob. Is job-dsl good enough for my purposes?
  

Thank you for the response. I am going to work without Multijob. Is job-dsl good enough for my purposes?