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

Computed Folder API poorly designed for concurrent event processing

      https://ci.jenkins.io/job/Tools/job/maven-hpi-plugin/view/change-requests/job/PR-53/  was build by a PR (mine) but on the job page there is no information about the job.

      BlueOcean shows a failed build with no information.

       

      If you follow the permalink (which takes you to build#1) then you can see the build exists and did indeed fail...

      rtyler has a support bundle - if you are workin on the ticket connect with him directly (as it has some private infor that is not available to anonymous users such as hostnames/ports etc...)

        1. job page.png
          job page.png
          278 kB
        2. build.png
          build.png
          349 kB
        3. build.log
          9 kB

          [JENKINS-42511] Computed Folder API poorly designed for concurrent event processing

          James Nord created issue -
          James Nord made changes -
          Attachment New: job page.png [ 36304 ]
          James Nord made changes -
          Attachment New: build.png [ 36305 ]
          James Nord made changes -
          Attachment New: build.log [ 36306 ]
          James Nord made changes -
          Environment Original: https://ci.jenkins.io/ New: https://ci.jenkins.io/ jenkins 2.46
          James Nord made changes -
          Description Original: [https://ci.jenkins.io/job/Tools/job/maven-hpi-plugin/view/change-requests/job/PR-53/]  was build by a PR (mine) but on the job page there is no information about the job.

          BlueOcean shows a failed build with no information.

           

          If you follow the permalink (which takes you to build#1) then you can see the build exists and did indeed fail...
          New: [https://ci.jenkins.io/job/Tools/job/maven-hpi-plugin/view/change-requests/job/PR-53/]  was build by a PR (mine) but on the job page there is no information about the job.

          BlueOcean shows a failed build with no information.

           

          If you follow the permalink (which takes you to build#1) then you can see the build exists and did indeed fail...

          [~rtyler] has a support bundle - if you are workin on the ticket connect with him directly (as it has some private infor that is not available to anonymous users such as hostnames/ports etc...)
          Jesse Glick made changes -
          Link New: This issue blocks JENKINS-23152 [ JENKINS-23152 ]
          Jesse Glick made changes -
          Labels Original: core pipeline New: pipeline
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          Summary Original: a job has a build but no history. New: ISE from RunMap.put
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            stephenconnolly Stephen Connolly
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: