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

Build Selector lastWithArtifacts() checks in the controller disk for existence of any artifacts for the build

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

      When I use s3CopyArtifact with buildSelector as lastWithArtifacts the method apparently the selector returns the latest build number that got some artifact on the disk and no artifact on S3. It should solely check if there is any artifact in S3 and return the latest build number that has at least one artifact in S3. 

       

          [JENKINS-70665] Build Selector lastWithArtifacts() checks in the controller disk for existence of any artifacts for the build

          Neel M created issue -
          Neel M made changes -
          Description Original: When I use {{s3CopyArtifact with buildSelector as }}{{lastWithArtifacts the method apparently the selector returns the latest build number that got some artifact on the disk and no artifact on S3. It should solely check if there is any artifact in S3 and return the latest build number that has at least one artifact in S3. }}

          {{}}
          New: When I use `s3CopyArtifact` with `buildSelector` as `lastWithArtifacts` the method apparently the selector returns the latest build number that got some artifact on the disk and no artifact on S3. It should solely check if there is any artifact in S3 and return the latest build number that has at least one artifact in S3. 

           
          Neel M made changes -
          Description Original: When I use `s3CopyArtifact` with `buildSelector` as `lastWithArtifacts` the method apparently the selector returns the latest build number that got some artifact on the disk and no artifact on S3. It should solely check if there is any artifact in S3 and return the latest build number that has at least one artifact in S3. 

           
          New: When I use {{s3CopyArtifact}} with {{buildSelector}} as {{lastWithArtifacts}} the method apparently the selector returns the latest build number that got some artifact on the disk and no artifact on S3. It should solely check if there is any artifact in S3 and return the latest build number that has at least one artifact in S3. 

           
          Neel M made changes -
          Summary Original: Build Selector lastWithArtifacts() checks in the controller disk for existence of any artifacts New: Build Selector lastWithArtifacts() checks in the controller disk for existence of any artifacts for the build

            jimilian Alexander A
            neel Neel M
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: