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

"Export as plain XML" option should allow exporting of all job history

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core

      When looking at the build history screen, the "export as plain xml" link only exports the most recent build for each job. The build history screen itself shows every build for each job. There is a need for a way to retrieve all builds for each job.

          [JENKINS-32274] "Export as plain XML" option should allow exporting of all job history

          Daniel Beck added a comment -

          It is not clear what this is about. Please provide more details.

          Daniel Beck added a comment - It is not clear what this is about. Please provide more details.

          Joshua Shinn added a comment -

          danielbeck As of now, "export as plain xml"(located on the build history screen, the link found on the main page of a jenkins instance) only exports the most recent build for each job. If you look at the data shown on this page, it is for every build ran for each job. So it doesn't make sense that "export as plain xml" only gives data for the most recent build for each job.

          Joshua Shinn added a comment - danielbeck As of now, "export as plain xml"(located on the build history screen, the link found on the main page of a jenkins instance) only exports the most recent build for each job. If you look at the data shown on this page, it is for every build ran for each job. So it doesn't make sense that "export as plain xml" only gives data for the most recent build for each job.

          Daniel Beck added a comment -

          This feature should probably be shot altogether. It's the Cruise Control compatibility feature.

          And FWIW, the format definition (archive.org because it's that obsolete) does not support the feature you're asking for anyway. So that would actually be a breaking change for the two people in the world still using this.

          Consider using the real Jenkins remote API instead.

          Daniel Beck added a comment - This feature should probably be shot altogether. It's the Cruise Control compatibility feature. And FWIW, the format definition (archive.org because it's that obsolete) does not support the feature you're asking for anyway. So that would actually be a breaking change for the two people in the world still using this. Consider using the real Jenkins remote API instead.

          I found a another issue:
          If you use the folder plugin and you organize your jobs in folders, then display the Build History View the correct data. But the Export as XML Displays no data!

          Christian Häussler added a comment - I found a another issue: If you use the folder plugin and you organize your jobs in folders, then display the Build History View the correct data. But the Export as XML Displays no data!

            Unassigned Unassigned
            joshshinn Joshua Shinn
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: