[JIRA] (JENKINS-53706) Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported
Title: Message Title Oleg Nenashev commented on JENKINS-53706 Re: Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported Fingerprinting is a Jenkins core functionality, is should not require https://plugins.jenkins.io/create-fingerprint . I agree there is a bug in the core somewhere if you get 404 before the build completes, but it has nothing to do with the Create Fingerprints plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53706) Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53706 Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53706) Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported
Title: Message Title
jlpinardon created an issue
Jenkins / JENKINS-53706
Fingerprinting Artifacts in a pipeline script without fingerprint plugin should be reported
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2018-09-21 12:30
Environment:
Jenkins 2.121.3 on a CentOS/7 machine.
Priority:
Trivial
Reporter:
jlpinardon
A jenkinsfile is coded with a post build artifact archiving step with fingerprinting such as :
success {
archiveArtifacts(
artifacts: "${env.JOB_BASE_NAME}_image/*.*",
fingerprint: true,
)
}
while the fingerprint plugin is not installed. The job succeed, and it is a good thing. Nevertheless, artifacts are displayed along with the fingerprint icons with a href which opens (for sure) a 404 error page. I think that when the fingerprint plugin is not installed or enabled, the icon must not be displayed, and also a message should be displayed in the console log.
