I\'m adding continuous integration to an EC2 project at work using Jenkins. The Jenkins machine itself is kept on an EC2 machine - one that might need to be taken offline an
Jenkins stores the configuration for each job within an eponymous directory in jobs/
. The job configuration file is config.xml
, the builds are stored in builds/
, and the working directory is workspace/
. See the Jenkins documentation for a visual representation and further details.
Jenkins 1.627, OS X 10.10.5
/Users/Shared/Jenkins/Home/jobs/{project_name}/config.xml
Am adding few things related to jenkins configuration files storage.
As per my understanding all config file stores in the machine or OS that you have installed jenkins.
The jobs you are going to create in jenkins will be stored in jenkins server and you can find the config.xml etc., here.
After jenkins installation you will find jenkins workspace in server.
*cd>jenkins/jobs/`
cd>jenkins/jobs/$ls
job1 job2 job3 config.xml ....*
The best approach would be to keep your job configurations in a Jenkinsfile that live in source control.
On Linux one can find the home directory of Jenkins looking for a file, that Jenkins' home contains, e.g.:
$ find / -name "config.xml" | grep "jenkins"
/var/lib/jenkins/config.xml
For the sake of completeness:
macOS High Sierra, Jenkins 2.x, installation via Homebrew
~/.jenkins/jobs/{project_name}/config.xml
Complete overview about jenkins home: https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins