-
Bug
-
Resolution: Fixed
-
Critical
If you look on the wiki describing the Slave To Master Access Control, there is a section on File access rules, where it says:
<BUILDDIR> can be used as a prefix to match your build record directory, such as /var/lib/jenkins/job/foo/builds/2014-10-17_12-34-56
However, Jenkins versions after 1.597 have a different home directory structure (see JENKINS-24380). The wiki page for Slave To Master Access Control reflects the old layout.
Can someone confirm (or otherwise) that the <BUILDDIR> token works in Jenkins both before and after 1.597, and update the wiki accordingly?
- is blocking
-
JENKINS-24380 Use build numbers as IDs
-
- Resolved
-
- is duplicated by
-
JENKINS-27053 Violations plugin incompatible with Slave To Master Access Control
-
- Resolved
-
- links to
The reason I think that there is an issue here, is that ${JENKINS_HOME}/secrets/filepath-filters.d/30-default.conf contains the following:
But, it's not working for me in Jenkins 1.597+ (see
JENKINS-27053) - I getslave may not mkdirs /exports/jenkins_home/jobs/Controls_TopUp_unittests/builds/439/violations
Is <BUILDDIR>/.+ correct in newer Jenkins?
I got the violations plugin to work by adding file secrets/filepath-filters.d/50-gui.conf containing this: