[JIRA] (JENKINS-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title
pigloves you created an issue
Jenkins / JENKINS-49569
Pipeline archives artifacts with weird untraceable folder name
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-02-15 03:36
Priority:
Major
Reporter:
pigloves you
Thanks for Blue Ocean plugin, it builds and archives artifacts in "${JENKINS_HOME}/jobs/${PROJ_NAME}/branches/${BRANCH_NAME}". But when a branch name contains "_(underscore)" or ".(dot)", it causes "${hyphened branch name}.${6 chars hash}" which I cannot utilize to deploy. Why does it happen? What's the best practice to use branch archives?
Add Comment
[JIRA] (JENKINS-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title pigloves you commented on JENKINS-49569 Re: Pipeline archives artifacts with weird untraceable folder name James Dumay Thank you for the explanation. Thing is, even if I name a plain branch name like "feature-1" and push commits several times, the branch names will be "feature-1_2" and "feature-1_3", which cause the path transformation, maybe because the "_(underscore)"s. It seems like I don't have the latter option to choose. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title pigloves you reopened an issue Jenkins / JENKINS-49569 Pipeline archives artifacts with weird untraceable folder name Change By: pigloves you Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title pigloves you commented on JENKINS-49569 Re: Pipeline archives artifacts with weird untraceable folder name In a company I'm working for, there is no SonaType-like repository. If there is "archiveArtifacts" function, please tell me how I can use the artifacts. At least please tell me what's the transformed path name so that I can use the artifacts. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title pigloves you commented on JENKINS-49569 Re: Pipeline archives artifacts with weird untraceable folder name James Dumay Please, it is not solved. Jenkinsfile has `archiveArtifacts` syntax. When we archive something, we want to use it. I need a way to trace the path like `Fix-2.27ittn`. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
