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

Lost builds historical data after updating to Jenkins v2.175

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • core, pipeline
    • None
    • Jenkins v2.175 / Unix master / Java 64bit 1.8.0_192

      I'm using Multibranch Pipeline to automatically build changes in my Enterprise GitHub Organization repositories.

      After updating Jenkins to 2.175 and restarting, ALL the successful builds of ALL the branches of ALL my GitHub org repositories (that's around 75 repositories and approximately 2,000 builds) have been retriggered and instantly failed. All the builds failed with the same error, see attached console log. Now, all the projects and branches and builds are marked as Failed, and some build information such as the build date appear to be lost (see screenshots).

      In the example log, we can see the build was successfully completed a week ago, but restarted and failed today after restarting Jenkins.  I can consistenly reproduce this issue by re-building a project and restarting Jenkins.

      The issue does not happen if I downgrade to Jenkins 2.174.

        1. failed_build_console_log.txt
          3 kB
        2. build_history.PNG
          build_history.PNG
          17 kB
        3. branches.PNG
          branches.PNG
          68 kB
        4. build_before.xml
          25 kB
        5. build_after.xml
          16 kB

            Unassigned Unassigned
            nico_echegut Nicolas Echegut
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: