Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14999

Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Error message:

      ...
      project_name=daily
      _=/bin/env
      Unable to find project for artifact copy: daily
      This may be due to incorrect project name or permission settings; see help for project name in job configuration.
      Build step 'Copy artifacts from another project' marked build as failure
      ...
      

      When I set the project name by hand, there is no error. When I use a build parameter, and set its value to the same value as the hand typed value, it fails. The above message show what variable I use: $project_name

      Please see the screenshots for the configuration details.

        Attachments

          Issue Links

            Activity

            Hide
            totoroliu Rick Liu added a comment -

            I have this same issue.

            Jenkins ver. 1.642.1
            Copy Artifact Plugin ver 1.37
            CloudBees Folders Plugin ver 5.1

            On the upstream trigger job,
            I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts"
            for the full downstream job name including Folder-Plugin's foldername "FOLDNER_NAME/DOWNSTREAM_PROJECT_NAME".

            But this still causes the error on the downstream job:
            ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME
            This may be due to incorrect project name or permission settings; see help for project name in job configuration.

            If on the upstream trigger job,
            I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts"
            for the full downstream job name to wildcard '*',
            then the problem solved.

            Show
            totoroliu Rick Liu added a comment - I have this same issue. Jenkins ver. 1.642.1 Copy Artifact Plugin ver 1.37 CloudBees Folders Plugin ver 5.1 On the upstream trigger job, I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts" for the full downstream job name including Folder-Plugin's foldername "FOLDNER_NAME/DOWNSTREAM_PROJECT_NAME". But this still causes the error on the downstream job: ERROR: Unable to find project for artifact copy: FOLDER_NAME/DOWNSTREAM_PROJECT_NAME This may be due to incorrect project name or permission settings; see help for project name in job configuration. If on the upstream trigger job, I have explicitly set "Permission to Copy Artifact - Projects to allow copy artifacts" for the full downstream job name to wildcard '*', then the problem solved.
            Hide
            totoroliu Rick Liu added a comment -

            After some further combination of trials,
            I found out that "Permission to Copy Artifact - Projects to allow copy artifacts" must set to a project name without FOLDER_NAME.

            This resolves the problem too.
            However,
            there's a misleading warning "Unable to find project:"
            when set the upstream job "Permission to Copy Artifact - Projects to allow copy artifacts"
            to a DOWNSTREAM_PROJECT_NAME only without FOLDER_NAME.

            I'll create a separate JIRA ticket for that.

            Show
            totoroliu Rick Liu added a comment - After some further combination of trials, I found out that "Permission to Copy Artifact - Projects to allow copy artifacts" must set to a project name without FOLDER_NAME. This resolves the problem too. However, there's a misleading warning "Unable to find project:" when set the upstream job "Permission to Copy Artifact - Projects to allow copy artifacts" to a DOWNSTREAM_PROJECT_NAME only without FOLDER_NAME. I'll create a separate JIRA ticket for that.
            Hide
            totoroliu Rick Liu added a comment -

            created JENKINS-33257 for the misleading warning

            Show
            totoroliu Rick Liu added a comment - created JENKINS-33257 for the misleading warning
            Hide
            jbochenski Jakub Bochenski added a comment -

            I'm still getting this in 1.3.7 / Jenkins ver. 1.651.1

            Show
            jbochenski Jakub Bochenski added a comment - I'm still getting this in 1.3.7 / Jenkins ver. 1.651.1
            Hide
            adelanre Lanre Ade added a comment -

            19 May 2016 - still having same issue. Rick's suggestion didn't work for me.

            Show
            adelanre Lanre Ade added a comment - 19 May 2016 - still having same issue. Rick's suggestion didn't work for me.

              People

              • Assignee:
                ikedam ikedam
                Reporter:
                deepchip Martin d'Anjou
              • Votes:
                2 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: