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

after creating a new pipeline that has Jenkinsfiles / PRs and branches you are told there are no branches with Jenkinsfile

    XMLWordPrintable

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      Blue Ocean 1.4 - beta 3, Blue Ocean 1.5 - beta 1

      Description

      create a new pipleine using git and https://github.com/apache/maven.git as the URL.

      When you are redirected to the pipeline you are told there are no branches containing Jenkinsfiles.

      This is so far from the truth

      Open a new window in classic and see that branch indexing is happily running and there are branches shown in classic view.

      switch between activity/branches and PRs notice that nothing ever updates.

      I had to reload the page to see the results.

      Video showing issue

        Attachments

          Issue Links

            Activity

            Hide
            kshultz Karl Shultz added a comment -

            That video is the greatest thing I've ever seen added to a defect, any place, ever. You just have to have the sound turned up to realize it.

            Show
            kshultz Karl Shultz added a comment - That video is the greatest thing I've ever seen added to a defect, any place, ever. You just have to have the sound turned up to realize it.
            Hide
            kshultz Karl Shultz added a comment -

            Testing Notes:

            • It'd be worthwhile to see if this can still be recreated. That video shows BO 1.1.4, and core 2.60.1.
            • Assuming it can be, any changes made should include unit tests to go along with them.
            • It's possible this is an example of how more complex Pipelines (or repositories, for that matter) could be useful for automated BO use cases. JENKINS-48125 open to track this very idea.
            Show
            kshultz Karl Shultz added a comment - Testing Notes: It'd be worthwhile to see if this can still be recreated. That video shows BO 1.1.4, and core 2.60.1. Assuming it can be, any changes made should include unit tests to go along with them. It's possible this is an example of how more complex Pipelines (or repositories, for that matter) could be useful for automated BO use cases. JENKINS-48125 open to track this very idea.
            Hide
            kshultz Karl Shultz added a comment -

            JFYI. I ran through this just now with BO 1.3.3 and Core 2.91. The branches are showing up just fine for me:

            But...I did see, briefly, the "You don't have any Jenkinsfiles" screen. It went by so quickly that I wasn't able to capture it, but it was there. So I wonder if maybe the underlying issue is still reproducible, just not as severe as it used to be?

            Show
            kshultz Karl Shultz added a comment - JFYI. I ran through this just now with BO 1.3.3 and Core 2.91. The branches are showing up just fine for me: But...I did see, briefly, the "You don't have any Jenkinsfiles" screen. It went by so quickly that I wasn't able to capture it, but it was there. So I wonder if maybe the underlying issue is still reproducible, just not as severe as it used to be?
            Hide
            imeredith Ivan Meredith added a comment -

            I've seen this before, last year....but I cant reproduce it after a lot of testing. This may be due to environment issues maybe its been fixed. Closing until its seen again.

            Show
            imeredith Ivan Meredith added a comment - I've seen this before, last year....but I cant reproduce it after a lot of testing. This may be due to environment issues maybe its been fixed. Closing until its seen again.

              People

              Assignee:
              imeredith Ivan Meredith
              Reporter:
              teilo James Nord
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: