I'm curious, now that this config setting is gone, and now there is the "jenkins.model.Jenkins.buildsDir" system property <https://www.jenkins.io/doc/book/managing/system-properties/>, are you now using that to separate your jobs/ from your builds/?
We're using Jenkins CasC to manage all jenkins configuration, and are trying to implement a solution for backing up and restoring build history, to provide build history continuity across promotions of jenkins clusters across dev/test/staging/prod environments. The previous plan was just to backup the jobs/ dir (we're using restic to make external backups from a simple hourly cron job), but since CasC also writes to this area, I'm thinking that separating jobs/ from builds/ in this way would provide some insurance against unforeseen conflicts of these two mechanisms interfering with one another. Thoughts? On Wednesday, March 29, 2017 at 6:47:20 AM UTC-7 [email protected] wrote: > Excellent! > Changing Build Record Root Directory in the system settings was exactly > what I was hoping for. > I never noticed that was there, assuming the setting has been there all > along.. > > My jobs folder is now a very managable size, containing pretty much just > the config.xml files, next build number, and a few symbolic links. > > Thanks! > > > On Friday, March 10, 2017 at 10:24:05 PM UTC-5, Christopher Orr wrote: >> >> On Thu, 9 Mar 2017, at 22:37, Gastro Man wrote: >> > Is it possible to configure Jenkins so the jobs' build history is not >> > contained in the same directory as the config.xml? >> > >> > Ideally, I would prefer all the configs to be together in an area >> > ("job_config" folder) that I can put in source control, backup, >> quickly >> > search and compare, and manage. >> > >> > And then the gigabytes of data stored in histories could be in another >> > location ("job_history" folder) where I don't care about source >> control, >> > don't need to include when searching across configs, etc. >> > Possibly even store this on a separate storage device.. >> > >> > I find it frustrating to have the mixing of "control" and "data" inside >> > every single job subfolder, but I haven't found a way around this so >> far. >> >> You could mark the "builds" subdirectories as ignored in source control? >> >> Or if you go to Manage Jenkins > Configure System and click "Advanced" >> at the top of the page, you'll be able to alter where build data is >> stored ("Build Record Root Directory"). >> >> If you change this to "${JENKINS_HOME}/builds/${ITEM_FULLNAME}", for >> example, then all of the build data will be stored there. >> >> At this point, the only thing left in ${JENKINS_HOME}/jobs/<name> (i.e. >> ${ITEM_ROOTDIR}) will be the job config.xml, and the metadata about >> build numbers and last success/failure symlinks etc.. >> >> Note that changing this value will not automagically migrate all of your >> existing data to the new location you've specified. >> >> Regards, >> Chris >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/171b5b4f-a15c-42a5-be3f-b57602c975een%40googlegroups.com.
