[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11701.1575427740223%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.7 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11693.1575424560299%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick commented on JENKINS-60040 Re: Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Reproduced in a functional test which passes when picking up a jclouds update with the fix of JCLOUDS-1447. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11578.1575413340252%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11580.1575413340285%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11570.1575411900275%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick started work on JENKINS-60040 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11572.1575411900333%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Luis Ortiz created an issue Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile Components: artifact-manager-s3-plugin Created: 2019-11-04 16:17 Environment: Jenkins 2.176.1, artifact-manager-s3-plugin 1.6 Priority: Major Reporter: Luis Ortiz When restarting a multi-branch pipeline job from a stage I noticed that the archived artifacts are not copied to the new pipeline run if the job name contains a forward slash. The archived artifacts are stored in S3 via the artifact manager s3 plugin. The s3 bucket that stores the artifacts has the / encoded as %2F and the artifact is successfully archived as I can see it in our AWS account. 09:48:25 Started by user 09:48:25 Restarted from build #1, stage Build environment 14:48:25 [2019-10-28T14:48:25.754Z] Connecting to https://github..com/api/v3 using /** (Token used for integration with GitHub Enterprise.) 09:48:26 Obtained Jenkinsfile from a1590de81a30e783b4327b83e5276c462f652086 09:48:27 09:48:27 GitHub has been notified of this commit's build result 09:48:27 09:48:27 org.jclouds.blobstore.KeyNotFoundException: /artifacts/shuttle-migrate/unstash-test/user%2Ftest/2/artifacts/test.txt not found in container .s3.amazonaws.com: The specified key
