Greetings!
While doing a clean up of our old build logs, I noticed that the
directory structure of the jobs directory seems a bit "suboptimal"
(although it's certainly simple):
https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins
JENKINS_HOME
+- ... configuration ...
+- jobs
+- [JOBNAME] (sub directory for each job)
+- [a] config.xml (job configuration file)
+- [b] workspace (working directory
+- [c] builds
+- [BUILD_ID] (for each build)
+- build.xml (build result summary)
+- log (log file)
+- changelog.xml (change log)
It appears to me that we have three different kinds of thing in a job
directory: a) job configuration, b) working space for SCM/compiler, c)
archive of build-logs
Was it ever considered (or is there a plugin) to make it possible to
split this, so that we (just a quick example) could have something like
this:
a) JENKINS_HOME
+- ... configuration ...
+- jobs
+- [JOBNAME] (sub directory for each job)
+- config.xml (job configuration file)
b) JENKINS_WORKSPACES
+- jobs
+- [JOBNAME] (sub directory for each job)
+- [b] workspace (working directory
c) JENKINS_BUILDS
+- jobs
+- [JOBNAME] (sub directory for each job)
+- [c] builds
+- [BUILD_ID] (for each build)
+- build.xml (build result summary)
+- log (log file)
+- changelog.xml (change log)
Reason I'm asking is because it seems to me to make sense to use
compressed/slow storage for the [builds] but a [workspace] should be on
fast storage to make builds fast.
It would also separate the configuration from the logs and workspaces.
I would be the first one to agree that this isn't a high priority
feature, but what are your thoughts on this?
cheers,
Martin
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
