Jenkins Copy Artifact Plugin

To use the plugin in a Jenkinsfile, you must utilize the `copyArtifacts` step within your pipeline script. You specify the `projectName` of the source job and define which artifacts you want to pull using the `filter` parameter. This allows your current build to seamlessly access files generated by a separate upstream job.

To prevent unauthorized access, the plugin uses a specific permission setting called "Copy Artifact" under the Job configurations. Administrators must explicitly grant the downstream job the right to copy artifacts from the upstream job. This permission can be managed via Role-Based Strategy or Project-based Matrix Authorization.

While the plugin natively focuses on moving artifacts between jobs on the same Jenkins controller or across Jenkins nodes, broader file transfers rely on related plugins. For external SFTP or SCP transfers, users typically use the "Publish Over SSH" or standard FTP plugins. The Copy Artifact Plugin itself is strictly for internal Jenkins workspace transfers.

This error usually occurs when the `projectName` parameter in your pipeline script does not exactly match the name of the upstream Jenkins job. It can also happen if the user running the downstream job lacks the necessary "Copy Artifact" permissions. Double-check your exact job names in the Jenkins dashboard and verify your access control settings.