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

incorrect message when viewing the "branches" of a vanilla pipeline.

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • blueocean-plugin
    • None
    • 1.0

      If you click the branches tab for a regular pipeline you get the following message...

      Branches are unsupported
      Branch runs only work with the Multibranch Pipeline job type. This is just one of the many reasons to switch to Jenkins Pipeline.

      However the last sentence is clearly incorrect. This job is a pipeline - and I have switched to pipeline - so it can not be a compelling reason to switch to Jenkins Pipeline - if pipelines do not support it.

      steps to reproduce

      • open Jenkins classic view
      • create an new Item
        • choose *Pipeline*
        • use the "Hello World" example
        • run a few builds
      • Open Blue Ocean
      • navigate to the pipeline you just created
      • click on "Branches"
      • Observer the error message....

          [JENKINS-42352] incorrect message when viewing the "branches" of a vanilla pipeline.

          James Nord created issue -
          James Nord made changes -
          Description Original: If you click the branches tab for a regular pipeline you get the following message...

          {quote}
          Branches are unsupported
          Branch runs only work with the Multibranch Pipeline job type. This is just one of the many reasons to switch to Jenkins Pipeline.
          {quote}

          However the last sentence is clearly incorrect. This job is a pipeline - and I have switched to pipeline - so it can not be a compelling reason to switch to Jenkins Pipeline - if pipelines do not support it.
          New: If you click the branches tab for a regular pipeline you get the following message...

          {quote}
          Branches are unsupported
          Branch runs only work with the Multibranch Pipeline job type. This is just one of the many reasons to switch to Jenkins Pipeline.
          {quote}

          However the last sentence is clearly incorrect. This job is a pipeline - and I have switched to pipeline - so it can not be a compelling reason to switch to Jenkins Pipeline - if pipelines do not support it.

          h2. steps to reproduce

          * open Jenkins classic view
          * create an new Item
          ** choose **Pipeline**
          ** use the "Hello World" example
          ** run a few builds
          * Open Blue Ocean
          * navigate to the pipeline you just created
          * click on "Branches"
          * Observer the error message....
          James Dumay made changes -
          Assignee New: James Dumay [ jamesdumay ]
          James Dumay made changes -
          Sprint New: 1.0 [ 221 ]
          James Dumay made changes -
          Rank New: Ranked lower
          James Dumay made changes -
          Link New: This issue duplicates JENKINS-41734 [ JENKINS-41734 ]
          James Dumay made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            jamesdumay James Dumay
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: