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

Does not export via JSON API

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • s3-plugin
    • None

      Users can get information on all build artifacts for non-S3 artifacts, via JENKINSURL/job/JOBNAME/api/json?depth=2

      With S3 artifacts, the relevant JSON is empty:

      "artifacts" : [

      ],

      And there's no JSON entry with information on where the S3 artifacts can be found.

          [JENKINS-29532] Does not export via JSON API

          Jo Shields added a comment -

          Initial implementation: https://github.com/directhex/s3-plugin/commit/cc4fba5b2031389c3b88a5eeb245bcf0eb03169f

          Current issues: It attaches inside actions[] rather than at the same depth (which is wrong) - there is an empty artifacts[] too for non-s3 artifacts. Maybe this should export a specific s3artifacts key? Would welcome ideas.

          Jo Shields added a comment - Initial implementation: https://github.com/directhex/s3-plugin/commit/cc4fba5b2031389c3b88a5eeb245bcf0eb03169f Current issues: It attaches inside actions[] rather than at the same depth (which is wrong) - there is an empty artifacts[] too for non-s3 artifacts. Maybe this should export a specific s3artifacts key? Would welcome ideas.

          Lars Bilke added a comment - - edited

          artifacts[] is still empty with s3-plugin 0.10.7

          sorry the S3 artifact info is available at e.g. .../api/json?pretty=true&tree=actions[artifacts[*]],url

          Lars Bilke added a comment - - edited artifacts[] is still empty with s3-plugin 0.10.7 sorry the S3 artifact info is available at e.g. .../api/json?pretty=true&tree=actions[artifacts [*] ],url

            Unassigned Unassigned
            directhex Jo Shields
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: