Symptoms: Trying to change an include pattern of a permission from the GUI default causes builds to fail with buildinfo deploy permission problems.
Steps to reproduce:
- Create a test user with no access to Artifactory, including build access
- Create a new permission target and use an Include Pattern to add a build
The example is for build "Maven-pipe" and uses "Maven**"
You should see the GUI move all builds matching the pattern to the "Included build" field
- Grant the test user access to publish buildinfo to this permission
- Run the build - Observe that the build fails with a 403
2019-07-12 19:11:01,223 [http-nio-8081-exec-9] [WARN ] (o.a.r.ArtifactoryResponseBase:125) - Sending HTTP error code 403: User jenkins is not permitted to deploy 'Maven-pipe/23-1562958637809.json' into 'artifactory-build-info:Maven-pipe/23-1562958637809.json'.
Workaround: Use "<PATTERN>/" to use wildcards. It looks like between Artifactory 6.8 and 6.10 the artifactory-build-info repository didn't exactly follow the documented include pattern system, and requires the full "path" to be used.