Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48571

checkout scm fails silently after "Could not determine exact tip revision of <branch>" in logs

      This Pipeline:

      pipeline {
          agent none
          options {
              buildDiscarder(logRotator(numToKeepStr: '10'))
              timeout(time: 1, unit: 'HOURS')
          }
          stages {
              stage('Test') {
                  failFast true
                  parallel {
                      stage('Debian Linux') {
                          agent { docker 'maven:slim' }
                          steps {
                              checkout scm
                              sh 'mvn test -B'
                          }
                          post {
                              always {
                                  junit testResults: '**/surefire-reports/**/*.xml', allowEmptyResults: true
                                  archiveArtifacts artifacts: '**/*.jar', fingerprint: true
                              }
                          }
                      }
                      stage('Alpine Linux') {
                          agent { docker 'maven:3-alpine' }
                          steps {
                              checkout scm
                              sh 'mvn test -B'
                          }
                          post {
                              always {
                                  junit testResults: '**/surefire-reports/**/*.xml', allowEmptyResults: true
                                  archiveArtifacts artifacts: '**/*.jar', fingerprint: true
                              }
                          }
                      }
                      stage('FreeBSD 11') {
                          agent { label 'freebsd' }
                          steps {
                              echo 'Code Valet does not currently support Maven on FreeBSD'
                          }
                      }
                  }
              }
          }
      }
      

      Doesn't seem to actually execute anything, here's the raw output of the run:

      Started by user R. Tyler Croy
      ERROR: Could not determine exact tip revision of defaults; falling back to nondeterministic checkout
      Checking out git https://github.com/rtyler/joni.git into /var/jenkins_home/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ@script to read Jenkinsfile
      Fetching changes from the remote Git repository
      Fetching without tags
      Checking out Revision 63d07e3559aece171ec6b7e5f4a595155ab99ac2 (origin/defaults)
      Commit message: "@abayer says to try this"
      Loading library pipeline-library@master
      Attempting to resolve master from remote references...
      Found match: refs/heads/master revision fecdabab952e9647b513c91367202e22e5161981
      Fetching changes from the remote Git repository
      Fetching without tags
      Checking out Revision fecdabab952e9647b513c91367202e22e5161981 (master)
      Commit message: "Make sure we check out scm, duh"
      Loading library inline-pipeline-secrets@master
      Attempting to resolve master from remote references...
      Found match: refs/heads/master revision 0b1840825b47d0a207151c22d49259b42f208728
      Fetching changes from the remote Git repository
      Fetching without tags
      Checking out Revision 0b1840825b47d0a207151c22d49259b42f208728 (master)
      Commit message: "Here be dragons"
      [Pipeline] timeout
      Timeout set to expire in 1 hr 0 min
      [Pipeline] {
      [Pipeline] stage
      [Pipeline] { (Test)
      [Pipeline] parallel
      [Pipeline] [Debian Linux] { (Branch: Debian Linux)
      [Pipeline] [Alpine Linux] { (Branch: Alpine Linux)
      [Pipeline] [FreeBSD 11] { (Branch: FreeBSD 11)
      [Pipeline] [Debian Linux] stage
      [Pipeline] [Debian Linux] { (Debian Linux)
      [Pipeline] [Alpine Linux] stage
      [Pipeline] [Alpine Linux] { (Alpine Linux)
      [Pipeline] [FreeBSD 11] stage
      [Pipeline] [FreeBSD 11] { (FreeBSD 11)
      [Pipeline] [FreeBSD 11] node
      [Pipeline] [Debian Linux] node
      [Debian Linux] Running on docker-ubuntuab9e60 in /home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ
      [Pipeline] [Alpine Linux] node
      [Pipeline] [Debian Linux] {
      [Pipeline] [Debian Linux] sh
      [Debian Linux] [joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ] Running shell script
      [Debian Linux] + docker inspect -f . maven:slim
      [Debian Linux] 
      [Debian Linux] Error: No such object: maven:slim
      [Pipeline] [Debian Linux] sh
      [Debian Linux] [joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ] Running shell script
      [Debian Linux] + docker pull maven:slim
      [Debian Linux] slim: Pulling from library/maven
      [Debian Linux] e7bb522d92ff: Pulling fs layer
      [Debian Linux] acf3a7df1b51: Pulling fs layer
      [Debian Linux] c1c98005fcff: Pulling fs layer
      [Debian Linux] 39dcc90226db: Pulling fs layer
      [Debian Linux] 23649b2102b0: Pulling fs layer
      [Debian Linux] dc6f0e3cd819: Pulling fs layer
      [Debian Linux] a1b832f08af6: Pulling fs layer
      [Debian Linux] 85571d835004: Pulling fs layer
      [Debian Linux] 26c8abdc6384: Pulling fs layer
      [Debian Linux] d11ca4afc9f8: Pulling fs layer
      [Debian Linux] 39dcc90226db: Waiting
      [Debian Linux] 23649b2102b0: Waiting
      [Debian Linux] dc6f0e3cd819: Waiting
      [Debian Linux] a1b832f08af6: Waiting
      [Debian Linux] 85571d835004: Waiting
      [Debian Linux] 26c8abdc6384: Waiting
      [Debian Linux] d11ca4afc9f8: Waiting
      [Debian Linux] c1c98005fcff: Verifying Checksum
      [Debian Linux] c1c98005fcff: Download complete
      [Debian Linux] acf3a7df1b51: Verifying Checksum
      [Debian Linux] acf3a7df1b51: Download complete
      [Debian Linux] e7bb522d92ff: Verifying Checksum
      [Debian Linux] e7bb522d92ff: Download complete
      [Debian Linux] 39dcc90226db: Verifying Checksum
      [Debian Linux] 39dcc90226db: Download complete
      [Debian Linux] dc6f0e3cd819: Download complete
      [Debian Linux] a1b832f08af6: Verifying Checksum
      [Debian Linux] a1b832f08af6: Download complete
      [Debian Linux] 85571d835004: Verifying Checksum
      [Debian Linux] 85571d835004: Download complete
      [Debian Linux] 26c8abdc6384: Verifying Checksum
      [Debian Linux] 26c8abdc6384: Download complete
      [Debian Linux] d11ca4afc9f8: Download complete
      [Debian Linux] 23649b2102b0: Verifying Checksum
      [Debian Linux] 23649b2102b0: Download complete
      [Debian Linux] e7bb522d92ff: Pull complete
      [Debian Linux] acf3a7df1b51: Pull complete
      [Debian Linux] c1c98005fcff: Pull complete
      [Debian Linux] 39dcc90226db: Pull complete
      [Debian Linux] 23649b2102b0: Pull complete
      [Debian Linux] dc6f0e3cd819: Pull complete
      [Debian Linux] a1b832f08af6: Pull complete
      [Debian Linux] 85571d835004: Pull complete
      [Debian Linux] 26c8abdc6384: Pull complete
      [Debian Linux] d11ca4afc9f8: Pull complete
      [Debian Linux] Digest: sha256:029478613539ddc6ed15bb267e60285500fdd2a505aa08479583d481a6ba5a20
      [Debian Linux] Status: Downloaded newer image for maven:slim
      [FreeBSD 11] Still waiting to schedule task
      [FreeBSD 11] freebsd-11-3a49c0 is offline
      [Alpine Linux] Still waiting to schedule task
      [Alpine Linux] Waiting for next available executor on docker
      [Pipeline] [Debian Linux] withDockerContainer
      [Debian Linux] docker-ubuntuab9e60 does not seem to be running inside a container
      [Debian Linux] $ docker run -t -d -u 1000:1000 -w /home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ -v /home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ:/home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ:rw,z -v /home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ@tmp:/home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** --entrypoint cat maven:slim
      [Pipeline] [Debian Linux] {
      Post stage
      [Pipeline] [Debian Linux] junit
      [Debian Linux] Recording test results
      [Pipeline] [Debian Linux] archiveArtifacts
      [Debian Linux] Archiving artifacts
      [Pipeline] [Debian Linux] }
      [Debian Linux] $ docker stop --time=1 0e293d2e7e2c7658f2453c28be97784ebc685ba457b8041c72456a4d3d4f4f71
      [Debian Linux] $ docker rm -f 0e293d2e7e2c7658f2453c28be97784ebc685ba457b8041c72456a4d3d4f4f71
      [Pipeline] [Debian Linux] // withDockerContainer
      [Alpine Linux] Running on docker-ubuntuab9e60 in /home/azureuser/workspace/workspace/joni_defaults-MBT2YSTY7MUAHVKKYHYN6TISLWL6VSKQMMQ2D2GOPWZJSC72ENZQ
      [Pipeline] [Debian Linux] }
      [Pipeline] [Debian Linux] // node
      [Pipeline] [Alpine Linux] {
      [Pipeline] [Debian Linux] }
      [Pipeline] [Debian Linux] // stage
      [Pipeline] [Debian Linux] }
      [Debian Linux] Failed in branch Debian Linux
      [Pipeline] [Alpine Linux] }
      [Pipeline] [FreeBSD 11] // node
      [Pipeline] [Alpine Linux] // node
      [Pipeline] [Alpine Linux] }
      [Pipeline] [FreeBSD 11] }
      [Pipeline] [Alpine Linux] // stage
      [Pipeline] [FreeBSD 11] // stage
      [Pipeline] [Alpine Linux] }
      [Alpine Linux] Failed in branch Alpine Linux
      [Pipeline] [FreeBSD 11] }
      [FreeBSD 11] Failed in branch FreeBSD 11
      [Pipeline] // parallel
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] }
      [Pipeline] // timeout
      [Pipeline] End of Pipeline
      ERROR: Could not determine exact tip revision of defaults
      Finished: ABORTED
      

      Plugins built into Code Valet:

      build/repos/apache-httpcomponents-client-4-api-plugin,b632272042139465076fa378e81f3fee729f885f
      build/repos/authentication-tokens-plugin,2a38368d4d9f61a6db0fde5b2f551293fc659cfe
      build/repos/azure-commons-plugin,b585a8f787f57e5552063db224e04a54454c1c87
      build/repos/azure-credentials-plugin,6ea5592773ad84f2f48854d1c611e1a529a22a9d
      build/repos/azure-vm-agents-plugin,e92e1955107b74be9536be2f57d1025966f9dde8
      build/repos/blueocean-autofavorite-plugin,0ddd2f7ea21c83d11a994ae569c56f970e7ba926
      build/repos/blueocean-display-url-plugin,d6515117712c9b30a32f32bb6e1a977711b9b037
      build/repos/blueocean-plugin,bb34e738f8430643086cdc8ac686d681ec90f9e1
      build/repos/branch-api-plugin,661e921eef2977970585829a691cbc0595dffea1
      build/repos/cloudbees-bitbucket-branch-source-plugin,b34bd66c7db1ce4f8b2abeb719530d7f7468cbc4
      build/repos/cloudbees-folder-plugin,afddb64d3704a3a7d2a87f8280f8748416b77b2d
      build/repos/cloud-stats-plugin,701ba1e7bf000e05fa5b436961f6125fbafa2e7c
      build/repos/credentials-binding-plugin,4d6f4c44baaa5aa1dd82a7b64ce4d8990a43d2fe
      build/repos/credentials-plugin,412ee9702029dc48bb7406fa9318ef8f2fc49b76
      build/repos/datadog-plugin,accf6ab44532c79613347416d5397c4156572cd4
      build/repos/display-url-api-plugin,e00542dea8bd0ee339863a11f5b61b872c3eacbd
      build/repos/docker-commons-plugin,b34c6f3ca4216eb66b09af6eef73db5f3c33adc2
      build/repos/docker-workflow-plugin,0e95d9409eb7d219dd9f4f37383c5321c630b889
      build/repos/durable-task-plugin,275ad653f71d89008ff061f6d8133d6684dcb1ad
      build/repos/embeddable-build-status-plugin,df555760b1a669a9acd558c5a498970bcf7febbe
      build/repos/favorite-plugin,08dcfd6b4fcb2b7c25efdf9ae995d0fedb8acdc2
      build/repos/git-client-plugin,5526a61878c1c789b545e0a81eecac859aca87b6
      build/repos/github-api-plugin,182e264acf362cf973362988cdfb24cb74738fab
      build/repos/github-branch-source-plugin,08b3d320281c74ef41c4d8ee064623fa75179c1d
      build/repos/github-oauth-plugin,5ad606efeedfd9ede0cbde31ec608ea1ba90ced1
      build/repos/github-plugin,68ceb5960549c6a5ce55c5288c7eaabbbb3719a2
      build/repos/git-plugin,828ca74769783d2ccd2c16ce038a87cacc66e140
      build/repos/git-server-plugin,1762ba8ccf3c7a46a607b912736912b784a63524
      build/repos/htmlpublisher-plugin,f187d56a4cd3fdcba69d0abc9deaac5be072d2d5
      build/repos/jackson2-api-plugin,74355ea21dacf9e948724d10c9abca0e2c3296bf
      build/repos/jira-plugin,4c7dcde762b55beca74176ec5e837d1784a81ae7
      build/repos/jsch-plugin,dfa3a710c4827896269302503ae86ae026d202f0
      build/repos/js-libs-plugin,79ca191724036878a88f13325851af14b0c70452
      build/repos/junit-plugin,0061cf267c63f6bb64bc165f395e01c0c8c38fd5
      build/repos/kubernetes-plugin,ec7d74f8782941d2b146193ebb14ae6ef5da9a46
      build/repos/lockable-resources-plugin,14b1abaddf441da9a20e8b1e0d94844550529a1e
      build/repos/mailer-plugin,18b8274e1a31b60d7e20492f1ecfa39483b90b37
      build/repos/matrix-auth-plugin,9c859ed3ea932024e73f665400457cbf106b8dcf
      build/repos/matrix-project-plugin,9e4d3bf904094986ea111a90a0c2c14019e2dd7f
      build/repos/mercurial-plugin,f6e5f0bff2d8678c0e7cb13d0db031b45c7a0437
      build/repos/pipeline-build-step-plugin,2e4012ecac352d248ca42feaa18c59aabfe2fa2c
      build/repos/pipeline-graph-analysis-plugin,7ea371dc90fef8e4f0627a365320fceec67f089f
      build/repos/pipeline-input-step-plugin,7aea2abf486438200cb1ae3fb553311d7ced11e0
      build/repos/pipeline-milestone-step-plugin,f7ef68f74aa1e923bb6ca3cdd10541fa6040f123
      build/repos/pipeline-model-definition-plugin,32c5e4178c89faca3ad184b4030d8f403425bdac
      build/repos/pipeline-stage-step-plugin,addb287b9d5b81f3d4ab3b15fb6dd33e7370062a
      build/repos/pipeline-stage-view-plugin,f5ce1f768457c7ff18408e6a54cb84f47a6a4ed8
      build/repos/plain-credentials-plugin,da51ba8703eefb201f3f6c4f4da3714fb83a37d6
      build/repos/pubsub-light-plugin,e374bc0248f37f6572e87913bf0c27cbf5b75d53
      build/repos/scm-api-plugin,45818a22f9d9846cfeb13d9c3f37d0b0dba15e04
      build/repos/script-security-plugin,38e6f6f7850b539a9a430d6ce5fd8c2e146a3181
      build/repos/sentry-plugin,a29347c83966fa0068a3c00af3fefcd9f19ed329
      build/repos/sse-gateway-plugin,685c6c709c96aa63f7d781c0df9060b9928e8b41
      build/repos/ssh-credentials-plugin,55e3d318eeddd52575b2ed632aa3841ba3b4834e
      build/repos/structs-plugin,eb9c1d5d5b1a9794925b62e17b9b4b1ee2113b13
      build/repos/token-macro-plugin,4d24aa5716f8d84e236824ab36d87c90a9897e8d
      build/repos/variant-plugin,3688261cf3c030b3eed603cf96e4758f79b569ac
      build/repos/workflow-aggregator-plugin,d67c39534f908f8432b44e588b0350b064e86bb5
      build/repos/workflow-api-plugin,bbab9280f0ce01988173ade26f8f349b14494499
      build/repos/workflow-basic-steps-plugin,3a464997109f0814f2399d15a2730e49ad74651c
      build/repos/workflow-cps-global-lib-plugin,aaa7ed1e04ce2ef751b2a770e71f0286c509ddc6
      build/repos/workflow-cps-plugin,861996956e7f931d6190af28fa0c0083d09b1d4d
      build/repos/workflow-durable-task-step-plugin,603b62f65ac5796a80b5598685b34ac30a644885
      build/repos/workflow-job-plugin,f3f45712196c9bea60101dbc8b804f6309f69cf2
      build/repos/workflow-multibranch-plugin,c49261f827d032a637475071ba6742f0c40a8653
      build/repos/workflow-scm-step-plugin,b9e8530ca4173b499a17af0468deace17139d458
      build/repos/workflow-step-api-plugin,0b984e5df55b88c39efb9a649e226fba48f5cb8f
      build/repos/workflow-support-plugin,5146dbf08bf4cfe84de9c6744ddfd18e5827b243
      

          [JENKINS-48571] checkout scm fails silently after "Could not determine exact tip revision of <branch>" in logs

          Alex Suter added a comment -

          I can confirm that when I save the multibranch build pipeline in the traditional jenkins ui (changing the description), the problem does not occur anymore after restart of jenkins.

          Alex Suter added a comment - I can confirm that when I save the multibranch build pipeline in the traditional jenkins ui (changing the description), the problem does not occur anymore after restart of jenkins.

          alexsuter you shouldn’t even need to change the description. Just clicking “Save” on the classic UI screen should suffice if BlueOcean created the job.

          You will need to repeat if BlueOcean updates the job config... and at that point you will get a rebuild storm (because BlueOcean is not round-tripping the ID)

          Stephen Connolly added a comment - alexsuter you shouldn’t even need to change the description. Just clicking “Save” on the classic UI screen should suffice if BlueOcean created the job. You will need to repeat if BlueOcean updates the job config... and at that point you will get a rebuild storm (because BlueOcean is not round-tripping the ID)

          vivek so thinking on this some more, my suggested simple fix for BlueOcean actually needs to be slightly more complex. There are already a significant number of exist jobs that were created by BlueOcean and either have a null id on disk (and are suffering from this issue) or have a non-null id on disk.

          If BlueOcean creates a new job, the simple fix is fine.

          If BlueOcean updates a job, it needs to round-trip the existing id if and only if the SCMSource type remains the same, otherwise it will trigger a rebuild storm on restart. To be clear, the rebuild storm on restart is an issue right now with BlueOcean even if using a version of the git plugin that ensures a non-null id in the constructor.

          So irrespective of everything else, BlueOcean needs to fix the round tripping of IDs during a configuration update... I claim BlueOcean is supposed to assign an ID during initial creation, but if you feel you have a strong argument to counter I am happy to hear it

          Stephen Connolly added a comment - vivek so thinking on this some more, my suggested simple fix for BlueOcean actually needs to be slightly more complex. There are already a significant number of exist jobs that were created by BlueOcean and either have a null id on disk (and are suffering from this issue) or have a non-null id on disk. If BlueOcean creates a new job, the simple fix is fine. If BlueOcean updates a job, it needs to round-trip the existing id if and only if the SCMSource type remains the same, otherwise it will trigger a rebuild storm on restart. To be clear, the rebuild storm on restart is an issue right now with BlueOcean even if using a version of the git plugin that ensures a non-null id in the constructor. So irrespective of everything else, BlueOcean needs to fix the round tripping of IDs during a configuration update... I claim BlueOcean is supposed to assign an ID during initial creation, but if you feel you have a strong argument to counter I am happy to hear it

          Michael Neale added a comment - - edited

          stephenconnolly  vivek I think open/save from classic is a perfectly fine work around for blue users. If blue is patched so new created pipelines are saved correctly, I still think it is ok to apply that fix/work around of open and save for older pipelines. 

          Whilst this issue was flagged originally by Tyler with codevalet and blue ocean creation, it seems most comments are from jobDSL users (who I think can fix it in the scripts?). So perhaps all that is needed is for blue ocean to do the right thing for new pipelines (older ones can be worked around), and perhaps some warning for jobDSL users that they need to set an id? 

          Also - nice sleuthing! this is a tricky one. 

           

          Michael Neale added a comment - - edited stephenconnolly   vivek I think open/save from classic is a perfectly fine work around for blue users. If blue is patched so new created pipelines are saved correctly, I still think it is ok to apply that fix/work around of open and save for older pipelines.  Whilst this issue was flagged originally by Tyler with codevalet and blue ocean creation, it seems most comments are from jobDSL users (who I think can fix it in the scripts?). So perhaps all that is needed is for blue ocean to do the right thing for new pipelines (older ones can be worked around), and perhaps some warning for jobDSL users that they need to set an id?  Also - nice sleuthing! this is a tricky one.   

          Vivek Pandey added a comment -

          >If BlueOcean updates a job, it needs to round-trip the existing id if and only if the SCMSource type remains the same, otherwise it will trigger a rebuild storm on restart.

          BlueOcean doesn't update a job. Even using API, if they try to create a new job for a gihub/bitbucket/git repo, it errors out if there is job with same name exists. Once user creates a blueocean pipeline job, at most they can do is to trigger re-indexing. So a simple solution of creating a blueocean specific id should be ok. 

          Vivek Pandey added a comment - >If BlueOcean  updates  a job, it needs to round-trip the existing id  if and only if  the SCMSource type remains the same, otherwise it will trigger a rebuild storm on restart. BlueOcean doesn't update a job. Even using API, if they try to create a new job for a gihub/bitbucket/git repo, it errors out if there is job with same name exists. Once user creates a blueocean pipeline job, at most they can do is to trigger re-indexing. So a simple solution of creating a blueocean specific id should be ok. 

          Vivek Pandey added a comment -

          BlueOcean PR: https://github.com/jenkinsci/blueocean-plugin/pull/1662. Its been merged to master.

          Vivek Pandey added a comment - BlueOcean PR: https://github.com/jenkinsci/blueocean-plugin/pull/1662 . Its been merged to master.

          Michael Neale added a comment -

          leoxs22 tr1z alexsuter ygorth

          Sorry for the drawn out things. 

          For users of JobDSL the solution/work around is to always set an id for the SCM, something like: 

          source {
           github {
           //github
           id "owner-${project_folder}:repo-${project_name}"

          This will then correct the behavior. Does this work for you? (similarly for other SCMs)

          If the jobs were created via some other way, then opening the config and saving it (no change needed) will fix it, and blue ocean has been patched to set the id correctly. 

           

          See sag47's last comment here: https://issues.jenkins-ci.org/browse/JENKINS-46290?focusedCommentId=329162&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329162 and his fix here: https://github.com/samrocketman/jervis/commit/e4cd6324ff22c3593d7e6feab88dff79e516e14b for an example of a jobDSL using it. 

          Michael Neale added a comment - leoxs22 tr1z alexsuter ygorth Sorry for the drawn out things.  For users of JobDSL the solution/work around is to always set an id for the SCM, something like:  source { github { //github id "owner-${project_folder}:repo-${project_name}" This will then correct the behavior. Does this work for you? (similarly for other SCMs) If the jobs were created via some other way, then opening the config and saving it (no change needed) will fix it, and blue ocean has been patched to set the id correctly.    See sag47 's last comment here: https://issues.jenkins-ci.org/browse/JENKINS-46290?focusedCommentId=329162&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329162  and his fix here: https://github.com/samrocketman/jervis/commit/e4cd6324ff22c3593d7e6feab88dff79e516e14b  for an example of a jobDSL using it. 

          Michael Neale added a comment -

          rtyler so far this looks like jobs created by blue ocean (before the fix) and jobDSLs without an id set get this, but as for the github organisation folder - are you seeing it there ? (it may have a related issue)

           

          stephenconnolly do you know if github organisation folders could be bitten by this, not setting the id correctly? 

          Michael Neale added a comment - rtyler so far this looks like jobs created by blue ocean (before the fix) and jobDSLs without an id set get this, but as for the github organisation folder - are you seeing it there ? (it may have a related issue)   stephenconnolly do you know if github organisation folders could be bitten by this, not setting the id correctly? 

          R. Tyler Croy added a comment -

          I could have sworn I saw this with the GitHub Organization Folders on ci.jenkins.io as well as from my Code Valet instances, but I cannot find any record of it.

          I might just be seeing ghosts in the machine, disregard

          R. Tyler Croy added a comment - I could have sworn I saw this with the GitHub Organization Folders on ci.jenkins.io as well as from my Code Valet instances, but I cannot find any record of it. I might just be seeing ghosts in the machine, disregard

          Michael Neale added a comment -

          ok good to know - I might close this now given the 'id' solution and the blue ocean fix. there is a linked follow on ticket to make the api (specifically for jobDSL) clearer here. Feel free to reopen if new information. 

          rtyler ok - well that fits with the theory, so that is good. 

          Michael Neale added a comment - ok good to know - I might close this now given the 'id' solution and the blue ocean fix. there is a linked follow on ticket to make the api (specifically for jobDSL) clearer here. Feel free to reopen if new information.  rtyler ok - well that fits with the theory, so that is good. 

            stephenconnolly Stephen Connolly
            rtyler R. Tyler Croy
            Votes:
            6 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: