• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: scm-api-plugin
• Labels:

  • fingerprints
  • scm

[JENKINS-7002] Revision fingerprinting

Elifarley created issue - 2010-07-16 08:46

Elifarley made changes - 2010-08-24 10:48

Description

Original: Given a revision, which builds happened at that revision (or changeset, for Mercurial projects) ? Fingerprints for revisions 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.

New: 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.

Jesse Glick made changes - 2010-09-28 13:48

Assignee

Original: Kohsuke Kawaguchi [ kohsuke ]

New: Jesse Glick [ jglick ]

Jesse Glick made changes - 2014-07-15 15:00

Component/s		New: core [ 15593 ]
Component/s	Original: subversion [ 15485 ]
Component/s	Original: mercurial [ 15502 ]
Labels		New: scm

Jesse Glick made changes - 2014-07-15 15:00

Assignee

Original: Jesse Glick [ jglick ]

R. Tyler Croy made changes - 2016-07-25 23:49

Workflow

Original: JNJira [ 137099 ]

New: JNJira + In-Review [ 174641 ]

Oleg Nenashev made changes - 2019-01-12 22:00

Component/s		New: scm-api-plugin [ 18054 ]
Component/s	Original: core [ 15593 ]

Oleg Nenashev made changes - 2019-01-12 22:07

Labels

Original: scm

New: fingerprints scm