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

Couldn't find any revision to build for PR build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • atlassian-bitbucket-server-integration-plugin
    • None

      After updating to version 4.1.2, on one of our pipelines we have begun seeing an error
      ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
      At this point to our knowledge it is only happening on this specific pipeline, which does do some things differently than our other pipelines so I will do my best to describe how it is configured.

      This pipeline is configured with the following behaviors 

      The main differences here compared to most of our other pipelines is the checkout timeout and Git LFS usage. The other key difference is that this pipeline is configured to skip the default checkout and does its checkout using a checkout step using the GitSCM class, configured as such

      checkout([
            $class: 'GitSCM',
            branches: scm.branches,
            doGenerateSubmoduleConfigurations: false,
            extensions: [
                [$class: 'CloneOption', depth: 50, noTags: false, shallow: true],
                [$class: 'GitLFSPull']
            ],
            submoduleCfg: [],
            userRemoteConfigs: scm.userRemoteConfigs
        ])

       

        1. image-2025-01-03-22-12-01-380.png
          image-2025-01-03-22-12-01-380.png
          29 kB

          [JENKINS-75088] Couldn't find any revision to build for PR build

          Brady Shober created issue -
          pin-yi made changes -
          Description Original: After updating to version 4.1.2, on one of our pipelines we have begun seeing an error
          ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
          At this point to our knowledge it is only happening on this specific pipeline, which does do some things differently than our other pipelines so I will do my best to describe how it is configured.

          This pipeline is configured with the following behaviors 

          !image-2025-01-03-22-12-01-380.png!

          The main differences here compared to most of our other pipelines is the checkout timeout and Git LFS usage. The other key difference is that this pipeline is configured to skip the default checkout and does its checkout using a checkout step using the GitSCM class, configured as such


          {code:java}
          checkout([
                      $class: 'GitSCM',
                      branches: scm.branches,
                      doGenerateSubmoduleConfigurations: false,
                      extensions: [
                          [$class: 'CloneOption', depth: 50, noTags: false, shallow: true],
                          [$class: 'GitLFSPull']
                      ],
                      submoduleCfg: [],
                      userRemoteConfigs: scm.userRemoteConfigs
                  ]) {code}
                      		New: {color:red}colored text{color}After updating to version 4.1.2, on one of our pipelines we have begun seeing an error
          ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
          At this point to our knowledge it is only happening on this specific pipeline, which does do some things differently than our other pipelines so I will do my best to describe how it is configured.

          This pipeline is configured with the following behaviors 

          !image-2025-01-03-22-12-01-380.png!

          The main differences here compared to most of our other pipelines is the checkout timeout and Git LFS usage. The other key difference is that this pipeline is configured to skip the default checkout and does its checkout using a checkout step using the GitSCM class, configured as such


          {code:java}
          checkout([
                      $class: 'GitSCM',
                      branches: scm.branches,
                      doGenerateSubmoduleConfigurations: false,
                      extensions: [
                          [$class: 'CloneOption', depth: 50, noTags: false, shallow: true],
                          [$class: 'GitLFSPull']
                      ],
                      submoduleCfg: [],
                      userRemoteConfigs: scm.userRemoteConfigs
                  ]) {code}
           
          pin-yi made changes -
          Description Original: {color:red}colored text{color}After updating to version 4.1.2, on one of our pipelines we have begun seeing an error
          ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
          At this point to our knowledge it is only happening on this specific pipeline, which does do some things differently than our other pipelines so I will do my best to describe how it is configured.

          This pipeline is configured with the following behaviors 

          !image-2025-01-03-22-12-01-380.png!

          The main differences here compared to most of our other pipelines is the checkout timeout and Git LFS usage. The other key difference is that this pipeline is configured to skip the default checkout and does its checkout using a checkout step using the GitSCM class, configured as such


          {code:java}
          checkout([
                      $class: 'GitSCM',
                      branches: scm.branches,
                      doGenerateSubmoduleConfigurations: false,
                      extensions: [
                          [$class: 'CloneOption', depth: 50, noTags: false, shallow: true],
                          [$class: 'GitLFSPull']
                      ],
                      submoduleCfg: [],
                      userRemoteConfigs: scm.userRemoteConfigs
                  ]) {code}
                      		New: After updating to version 4.1.2, on one of our pipelines we have begun seeing an error
          ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
          At this point to our knowledge it is only happening on this specific pipeline, which does do some things differently than our other pipelines so I will do my best to describe how it is configured.

          This pipeline is configured with the following behaviors 

          !image-2025-01-03-22-12-01-380.png!

          The main differences here compared to most of our other pipelines is the checkout timeout and Git LFS usage. The other key difference is that this pipeline is configured to skip the default checkout and does its checkout using a checkout step using the GitSCM class, configured as such
          {code:java}
          checkout([
                      $class: 'GitSCM',
                      branches: scm.branches,
                      doGenerateSubmoduleConfigurations: false,
                      extensions: [
                          [$class: 'CloneOption', depth: 50, noTags: false, shallow: true],
                          [$class: 'GitLFSPull']
                      ],
                      submoduleCfg: [],
                      userRemoteConfigs: scm.userRemoteConfigs
                  ]) {code}
           

            Unassigned Unassigned
            butter1484 Brady Shober
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: