• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • batch-task-plugin, core
    • None
    • 1.634 or higher + Batch Task Plugin

      The Batch task history panel is empty (Find pane only) since the 1.634 version.
      Maybe linked, a blocking bug has been introduced within the 1.633 version (cf. JENKINS-30820) that impeded to add any batch task on job.
      I guess the bug comes from the core but maybe the Batch Task Plugin should be upgraded

      Use case
      To reproduce:

      • install the Batch Tasks plugin
      • create an empty freestyle job with Batch tasks option (echo "Hello world")
      • run a build
      • run the task several times
      • look at the task build history (/job/<job name>/batchTasks/task/<task name>/)

      Tested with 1.616, 1.632: the batch history panel displayed all the builds.
      Tested with 1.633: cannot access to my job. Create a new one, cannot create Batch task because of ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver
      Tested with 1.634, 1.642.3: the batch history panel is empty (Find pane only)

          [JENKINS-33833] Lost the batch task history since 1.634

          Mikael Gaunin created issue -

          Daniel Beck added a comment -

          ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver

          envinject is not a dependency of Batch Tasks Plugin, so whatever is going on here, your steps to reproduce are incomplete.

          Daniel Beck added a comment - ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver envinject is not a dependency of Batch Tasks Plugin, so whatever is going on here, your steps to reproduce are incomplete.
          Mikael Gaunin made changes -
          Description Original: The Batch task history panel is empty (_Find pane only_) since the 1.634 version.
          Maybe linked, a blocking bug has been introduced within the 1.633 version (cf. JENKINS-30820) that impeded to add any batch task on job.
          I guess the bug comes from the core but maybe the [Batch Task Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin] should be upgraded (?)

          *Use case*
          To reproduce:
          * install the Batch Tasks plugin
          * create an empty freestyle job with Batch tasks option (_echo "Hello world"_)
          * run the task several times
          * look at the task build history (_/job/<job name>/batchTasks/task/<task name>/_)

          Tested with 1.616, 1.632: the batch history panel displayed all the builds.
          Tested with 1.633: cannot access to my job. Create a new one, cannot create Batch task because of _ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver_
          Tested with 1.634, 1.642.3: the batch history panel is empty (_Find pane only_)
          New: The Batch task history panel is empty (_Find pane only_) since the 1.634 version.
          Maybe linked, a blocking bug has been introduced within the 1.633 version (cf. JENKINS-30820) that impeded to add any batch task on job.
          I guess the bug comes from the core but maybe the [Batch Task Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin] should be upgraded (?)

          *Use case*
          To reproduce:
          * install the Batch Tasks plugin
          * create an empty freestyle job with Batch tasks option (_echo "Hello world"_)
          * run a build
          * run the task several times
          * look at the task build history (_/job/<job name>/batchTasks/task/<task name>/_)

          Tested with 1.616, 1.632: the batch history panel displayed all the builds.
          Tested with 1.633: cannot access to my job. Create a new one, cannot create Batch task because of _ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver_
          Tested with 1.634, 1.642.3: the batch history panel is empty (_Find pane only_)

          Mikael Gaunin added a comment -

          I assure you that the steps to reproduce are complete; with 1.632 (or older versions) and 1.634 (or newer versions) and without installing the EnvInject Plugin, you don't have this issue (ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver).
          As a remark, with the 1.633 version, we have the issue with or without the EnvInject Plugin.

          Mikael Gaunin added a comment - I assure you that the steps to reproduce are complete; with 1.632 (or older versions) and 1.634 (or newer versions) and without installing the EnvInject Plugin , you don't have this issue ( ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver ). As a remark, with the 1.633 version, we have the issue with or without the EnvInject Plugin .

          Daniel Beck added a comment -

          Weird.

          Anyway, I'm pretty sure the cause is JENKINS-26445.

          Daniel Beck added a comment - Weird. Anyway, I'm pretty sure the cause is JENKINS-26445 .
          Julien Carsique made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Julien Carsique added a comment - - edited

          This issue makes the batch tasks hard to use: while the task is not executing, you don't see the waiting build and cannot know if the build request worked or even happened.

          danielbeck, please link it with JENKINS-26445 if you think it's related. Why do you think so? Or maybe are you talking about one of it's subtasks or a side effect? JENKINS-26445 resolution dates and versions do not match. Did you mean that JENKINS-30899 introduced the regression?

          Julien Carsique added a comment - - edited This issue makes the batch tasks hard to use: while the task is not executing, you don't see the waiting build and cannot know if the build request worked or even happened. danielbeck , please link it with JENKINS-26445 if you think it's related. Why do you think so? Or maybe are you talking about one of it's subtasks or a side effect? JENKINS-26445 resolution dates and versions do not match. Did you mean that JENKINS-30899 introduced the regression?

          Daniel Beck added a comment -

          jcarsique The fix for JENKINS-26554 was introduced in 1.633, refined in 1.634, and changes how the sidepanel build history works. So, one of the two, but they're closely related.

          Daniel Beck added a comment - jcarsique The fix for JENKINS-26554 was introduced in 1.633, refined in 1.634, and changes how the sidepanel build history works. So, one of the two, but they're closely related.

          Mikael Gaunin added a comment - - edited

          I looked deeper into the code trying to understand the cause of the issue.
          I'm pretty sure that the changes on build history, pagination and so on, done by tfennelly (seen in Comparing changes 1.632...1.633), could explain the empty pane for batch tasks.
          Indeed, from the Batch Task Plugin, BatchRun extends Actionable only. I did a quick test to make this class extends Queue.Item, here the results:

          Not so good but Tom, maybe you see from where the issue comes from.
          Thanks for your help

          Mikael Gaunin added a comment - - edited I looked deeper into the code trying to understand the cause of the issue. I'm pretty sure that the changes on build history, pagination and so on, done by tfennelly (seen in Comparing changes 1.632...1.633 ), could explain the empty pane for batch tasks. Indeed, from the Batch Task Plugin , BatchRun extends Actionable only. I did a quick test to make this class extends Queue.Item, here the results: Not so good but Tom, maybe you see from where the issue comes from. Thanks for your help
          Mikael Gaunin made changes -
          Attachment New: BatchTasksBuildHistory_Queue.Item.png [ 32842 ]

            Unassigned Unassigned
            mgaunin Mikael Gaunin
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: