File fingerprints can tell which builds reference a given file.

      What about revisions?

      Given a revision, which builds happened at that revision (or changeset, for Mercurial projects) ?

      Revision fingerprints would provide an answer for this question.

      Remember that in the case of Mercurial changeset fingerprints, the user should only be asked about which changeset he/she wants to search for, since both build number AND job name can be derived from a changeset ID.

          [JENKINS-7002] Revision fingerprinting

          Jesse Glick added a comment -

          No idea if Hudson has a feature that the Mercurial plugin could hook into here. Patches welcome.

          Jesse Glick added a comment - No idea if Hudson has a feature that the Mercurial plugin could hook into here. Patches welcome.

          Jesse Glick added a comment -

          Would I think need to have core support.

          Jesse Glick added a comment - Would I think need to have core support.

          Oleg Nenashev added a comment -

          I believe it would be a part of SCM API Plugin now

          Oleg Nenashev added a comment - I believe it would be a part of SCM API Plugin now

            Unassigned Unassigned
            elifarley Elifarley
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: