I'm trying to replace the hardcoded requirements in our jenkins build specification with a requirements file.
We have already configured and used chroot plugin to run a build process which itself requires root permissions. However we don't want to manage the setup of that chroot environment in the job spec and instead control it from files in git.
In the job configuration, the chroot builder has a field for "Requirements Files". This appears to be the right thing to use. But when I fill this in I'm just given an error and cannot save the configuration:
File ImageBuilder/jenkins_env_requirements.txt does not yet exist.
I've confirmed that the file does exist in the repository and run a build against that repo for good measure:
$ ls -lh ImageBuilder/jenkins_env_requirements.txt
-rw-r--r-- 1 philip philip 28 Nov 25 14:56 ImageBuilder/jenkins_env_requirements.txt
It seems odd that this plugin tries to verify the existence of a file in a git repository while configuring the build, rather than while running the build. Have I misinterpreted where this file is supposed to live?
I'm trying to replace the hardcoded requirements in our jenkins build specification with a requirements file.
We have already configured and used chroot plugin to run a build process which itself requires root permissions. However we don't want to manage the setup of that chroot environment in the job spec and instead control it from files in git.
In the job configuration, the chroot builder has a field for "Requirements Files". This appears to be the right thing to use. But when I fill this in I'm just given an error and cannot save the configuration:
I've confirmed that the file does exist in the repository and run a build against that repo for good measure:
It seems odd that this plugin tries to verify the existence of a file in a git repository while configuring the build, rather than while running the build. Have I misinterpreted where this file is supposed to live?