• Type: Improvement
• Resolution: Fixed
• Priority: Major
• Component/s: maven-plugin
• Labels:

  • fingerprints
  • performance
• Environment:

  1.448

1. 

   FreeStylePublishers.png

   11 kB

   2012-01-23 14:25

2. 

   MavenJobPublishers.png

   5 kB

   2012-01-23 14:25

[JENKINS-11333] Make fingerprinting configurable in Maven projects

Stephan Pauxberger created issue - 2011-10-12 14:05

Andrew Bayer made changes - 2012-01-18 00:30

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Stephan Pauxberger made changes - 2012-01-23 14:06

Resolution	Original: Not A Defect [ 7 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Stephan Pauxberger made changes - 2012-01-23 14:08

Description	Original: Currently, in a Maven Project, fingerprints are generated for all build artifacts (created and used). In a freestyle project, you can manually select files to be fingerprinted using the Fingerprinter publisher. This needs to be possible for Maven Projects, too. Consider for example a Maven project that uses post-build steps to create additional artifacts. You con archive them (without them being fingerprinted), but you cannot choose to fingerprint them. Looking at hudson.tasks.Fringerprinter, I see no reason why this publisher should not be available for configuration. If you enter the publisher by hand into the config.xml of a job, it works (until you reconfig that job, of course). One small drawback: two fingerprintActions are included. Tasks: - make Fingerprinter available for Maven projects - prevent Fingerprinter from always creating a new FingerprintAction (i.e. let it check for any existing FingerprintActions (like MavenFingerprinter does)) the second part is trivial, I can create a pull request for that.	New: Currently, in a Maven Project, fingerprints are generated for all build artifacts (created and used). In a freestyle project, you can manually select files to be fingerprinted using the Fingerprinter publisher. This needs to be possible for Maven Projects, too. Consider for example a Maven project that uses post-build steps to create additional artifacts. You can archive them (without them being fingerprinted), but you cannot choose to fingerprint them. Looking at hudson.tasks.Fingerprinter, I see no reason why this publisher should not be available for configuration. If you enter the publisher by hand into the config.xml of a job, it works (until you reconfig that job, of course), so this seems to be a display issue. One small drawback: two fingerprintActions are included. Tasks: - make Fingerprinter available for Maven projects - prevent Fingerprinter from always creating a new FingerprintAction (i.e. let it check for any existing FingerprintActions (like MavenFingerprinter does)) the second part is trivial, I can create a pull request for that.
Environment		New: 1.448

Stephan Pauxberger made changes - 2012-01-23 14:25

Attachment		New: FreeStylePublishers.png [ 21437 ]
Attachment		New: MavenJobPublishers.png [ 21438 ]

Jesse Glick made changes - 2014-05-21 21:03

Labels		New: fingerprints performance
Summary	Original: Fingerprinter-Publisher should be available in Maven jobs	New: Make fingerprinting configurable in Maven projects

Jesse Glick made changes - 2014-05-21 21:04

Link

New: This issue is related to JENKINS-19712 [ JENKINS-19712 ]

Jesse Glick made changes - 2014-05-21 21:04

Link

New: This issue is related to JENKINS-11814 [ JENKINS-11814 ]

Jesse Glick made changes - 2014-05-21 21:16

Link

New: This issue depends on JENKINS-17606 [ JENKINS-17606 ]

Jesse Glick made changes - 2014-05-21 21:49

Assignee

New: Jesse Glick [ jglick ]

Jesse Glick made changes - 2014-05-21 21:49

Status

Original: Reopened [ 4 ]

New: Open [ 1 ]

Load more newer history items