DEV@cloud Backup Policies

DEV@cloud is a hosted solution that is comprised of several different services. CloudBees is not generally in the position to recover nor offer recovery of jobs, builds, configurations.

That said, CloudBees does maintain backups for operational use in the event of catastrophic failures.

The following outlines the services that we backup currently. These may change at any point in time without notice.


Jenkins configuration and build artifacts (the JENKINS_HOME) are backed up to S3 after changes occur within Jenkins. These backups are for disaster recovery only, so that if a Jenkins host is lost, no significant amount of data will be lost.

We also keep rotating backups for Jenkins, with historical versions as old as two weeks. These are for CloudBees operational use in the event that a bug in the system results in the corruption of your data. They are not available for recovery due to user error (deleting a job or similar).

Plugins like the Audit Trail Plugin and the JobConfigHistory Plugin are available to monitor modifications that are made by users.


We take regular (multiple times per day) snapshots of our storage however these are purely for disaster recovery purposes. These backups are then retained for a significant amount of time (with decreasing granularity - e.g. daily backups for a week, then weekly backups for a month).

CloudBees does not offer any standard way for the account owner to extract the data from the system (although you may use SVNSync / wget to pull down the repository).


Sonar databases are stored in a high availability MySQL service. This service is backed up for disaster recovery purposes on a daily basis.

Have more questions? Submit a request


Article is closed for comments.