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

Path of fingerprinted files not saved by CopyArtifacts

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Artifacts copied with CopyArtifact seem to not record full paths in fingerprints. Only the filename is recorded. This could be fine – except the "See Fingerprints" page seems to only display one line for each file name. (That's probably a bug too.)

      I would think that on the CopyArtifacts side, it should be quite a simple fix, in FingerprintingCopyMethod.java, which seems to be recording fingerprints with s.getName(). My quick guess is that the whole path could be stored if s.getName() was replaced with something like s.toString()...

        Attachments

          Activity

          Hide
          jwal James Ascroft-Leigh added a comment -

          I noticed this too but I actually use this feature. I have carefully configured my jobs so that...

          • All files that are archived are in a folder so they have at least one "/" in their path.
          • All files that are consumed by a downstream project have a unique filename.

          I then use the presence of a "/" in the fingerprint filename in the build.xml file to distinguish between artifacts generated by a build and artifacts consumed by it. I know it is a horrible hack but it allows me to detect statically when a build needs to be rerun due to an updated upstream artifact.

          I'd love to hear a better suggestion for how to do this.

          Show
          jwal James Ascroft-Leigh added a comment - I noticed this too but I actually use this feature. I have carefully configured my jobs so that... All files that are archived are in a folder so they have at least one "/" in their path. All files that are consumed by a downstream project have a unique filename. I then use the presence of a "/" in the fingerprint filename in the build.xml file to distinguish between artifacts generated by a build and artifacts consumed by it. I know it is a horrible hack but it allows me to detect statically when a build needs to be rerun due to an updated upstream artifact. I'd love to hear a better suggestion for how to do this.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jakobmalm Jakob Malm
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: