You can update configurations in one of following ways:
Checking projects and clicking "Migrate the selected project(s)" updates configurations adding appropriate "Permission to Copy Artifact" configurations to the projects listed in "Project with the artifacts".
Automatic migration is not applicable to some kind of projects that generate configurations automatically, such as multibranch. Please apply manual migrations to those projects.
You can migrate projects updating configurations manually.
The updated project will be removed from the list automatically when the project is built again and it wouldn't fail in Production mode. You can see whether the project is built again after updating the configuration with checking "Last time" field. Auto removal is performed only in Migration mode, and you have to remove it manually after you switch Copy Artifact to Production mode.
You can configure appropriate permissions for Copy Artifact in one of following ways:
You can configure "Permission to Copy Artifact" to the project with artifacts to define which projects are allowed to copy artifacts from that project. "Migrate the selected project(s)" button does this configuration automatically.
In pipelines, you can define copyArtifactPermission
like this:
pipeline {
agent any;
options {
// specify projects to allow to copy artifacts with a comma-separated list.
copyArtifactPermission('job1,job2,...');
}
stages{...}
}
properties([
// specify projects to allow to copy artifacts with a comma-separated list.
copyArtifactPermission('job1,job2,...'),
]);
node {
...
}
You can configure "Access Control for Builds" in Manage Jenkins > Configure Global Security so that builds run with authentication allowed to access builds with artifacts.
That configuration is shown only when plugins providing "Access Control for Builds" features are installed.
See following pages for more details about "Access Control for Builds":