Home/ Questions/Q 5942647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T16:17:00+00:00

I’m adding continuous integration to an EC2 project at work using Jenkins. The Jenkins

  • 0

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 and brought back on an entirely different EC2 instance at any point. We have a bunch of Puppet manifests allowing us to easily reinstall the software on the EC2 instance, but custom configuration files, like the ones for the jobs I create in Jenkins, would be deleted after the move.

Now, if Jenkins stores what jobs are to be run on it in an XML file or set of XML files somewhere, I could set up a system where those files are committed to the version control server, and then downloaded back to a newly-created server as part of the puppet manifest. Does anyone know where these files are stored? I’ve tried copying /var/lib/jenkins/jobs, but that appears to store the output of Jenkins’ jobs, not the input.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Jenkins stores some of the related builds data like the following:

    • The working directory is stored in the directory {JENKINS_HOME}/workspace/.

      • Each job store its related temporal workspace folder in the directory
        {JENKINS_HOME}/workspace/{JOBNAME}

    • The configuration for all jobs stored in the directory {JENKINS_HOME}/jobs/.

      • Each job store its related builds data in the directory
        {JENKINS_HOME}/jobs/{JOBNAME}

      • Each job folder contains:

        • The job configuration file is {JENKINS_HOME}/jobs/{JOBNAME}/config.xml

        • The job builds are stored in {JENKINS_HOME}/jobs/{JOBNAME}/builds/

    See the Jenkins documentation for a visual representation and further details.

    JENKINS_HOME
 +- config.xml     (jenkins root configuration)
 +- *.xml          (other site-wide configuration files)
 +- userContent    (files in this directory will be served under your http://server/userContent/)
 +- fingerprints   (stores fingerprint records)
 +- nodes          (slave configurations)
 +- plugins        (stores plugins)
 +- secrets        (secretes needed when migrating credentials to other servers)
 +- workspace (working directory for the version control system)
     +- [JOBNAME] (sub directory for each job)
 +- jobs
     +- [JOBNAME]      (sub directory for each job)
         +- config.xml     (job configuration file)
         +- latest         (symbolic link to the last successful build)
         +- builds
             +- [BUILD_ID]     (for each build)
                 +- build.xml      (build result summary)
                 +- log            (log file)
                 +- changelog.xml  (change log)
    • 0