[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title ikedam updated JENKINS-39174 This was fixed in copyartifact-1.42.1. Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Change By: ikedam Status: Open Fixed but Unreleased Assignee: James Femia Resolution: Fixed Released As: copyartifact-1.42.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title ikedam updated JENKINS-39174 Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Change By: ikedam Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.175597.1477058513000.2126.1583564221051%40Atlassian.JIRA.
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title Steve Mokris commented on JENKINS-39174 Re: Help text for projectName does not describe all permitted values I drafted a wiki page based on Jesse Glick's comments: https://wiki.jenkins.io/display/JENKINS/How+to+reference+another+project+by+name …and a PR: https://github.com/jenkinsci/copyartifact-plugin/pull/107 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-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia edited a comment on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the *url-encoded* name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy.e.g. if I have a Multibranch project called "MyBranches", with base of {{https://my.repo}}, and I tell it to search for branches in {{/branches/jamie/*}} and it finds {{/branches/jamie/a}} and {{/branches/jamie/b}}, copying artifacts from these jobs requires me to use {{/MyBranches/branches%2Fjamie%2Fa}}.As a side node on that, unless I am using {{java.net.URLEncoder}} wrong, I have to replace the output of encode {{+}} with {{%20}} in order for the string to match the job name if it has spaces in the url path .{noformat}def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/ a spaces in path ', 'UTF-8').replace('+', '%20'){noformat}I also did not know that the *Pipeline Syntax* link from different pages affected the behaviour of the snippet generator.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia commented on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the url-encoded name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy. e.g. if I have a Multibranch project called "MyBranches", with base of https://my.repo, and I tell it to search for branches in /branches/jamie/* and it finds /branches/jamie/a and /branches/jamie/b, copying artifacts from these jobs requires me to use /MyBranches/branches%2Fjamie%2Fa. As a side node on that, unless I am using java.net.URLEncoder wrong, I have to replace the output of encode + with %20 in order for the string to match the job name.
def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/a', 'UTF-8').replace('+', '%20')
I also did not know that the Pipeline Syntax link from different pages affected the behaviour of the snippet generator.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title Jesse Glick commented on JENKINS-39174 Re: Help text for projectName does not describe all permitted values Well, the syntax offered is going to depend on where you clicked the Pipeline Syntax link; it will offer a path valid from that point. In the case of a multibranch project, you probably want to run it from a sample branch project, so for example from qatest/master you could refer to dev/releases as either /dev/releases or ../../dev/releases. Just like Unix filesystem paths. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39174) Help text for projectName does not describe all permitted values
Title: Message Title Mark Stosberg commented on JENKINS-39174 Re: Help text for projectName does not describe all permitted values I ran into this as well and was also only able to resolve it with help from @jglick in #jenkins. In my case, I was trying to copy artifacts from the branch of a multipline build. The Pipeline syntax generated only generated syntax that included the projectName as "My Pipeline". The correct syntax I eventually figured out was "/My Pipeline/mybranch". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39174) Help text for projectName does not describe all permitted values
Title: Message Title James Femia created an issue Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2016/Oct/21 2:01 PM Environment: Jenkins 2.19.1 LTS / Copy Artifact Plugin 1.38.1 Labels: documentation pipeline Priority: Minor Reporter: James Femia According to jglick in #jenkins, the projectName parameter for Copy Artifact can accept absolute and relative paths to jobs in folders. There is no mention of this anywhere in the user-facing documentation. Add Comment
