configuration files to a previous state. Configuration is straightforward (see Figure 13.12, “Configuring
the Thin Backup plugin”), and simply involves scheduling full and incremental backups using a cron
job syntax, and providing a directory in which to store the backups.
Figure 13.12. Configuring the Thin Backup plugin
To restore a previous configuration, just go to the Restore page and choose the date of the configuration
you wish to reinstate (see Figure 13.13, “Restoring a previous configuration”). Once the configuration
has been restored to the previous state, you need to reload the Jenkins configuration from disk or restart
Jenkins.
Figure 13.13. Restoring a previous configuration
13.5. Archiving Build Jobs
Another way to address disk space issues is to delete or archive projects that are no longer active.
Archiving a project allows you to easily restore it later if you need to consult the project data or artifacts.
Archiving a project is simple: just move the build project directory out of the job directory. Of course,
typically, you would compress it into a ZIP file or a tarball first.
In the following example, we want to archive the tweeter-default project. So first we go to the Jenkins
jobs directory and create a tarball (compressed archive) of the tweeter-default build job directory:
$ cd $JENKINS_HOME/jobs
$ ls