Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

(replies inline) On Wed, 21 Mar 2018, Baptiste Mathus wrote: > FYI JEP now officially filed for review at > https://github.com/jenkinsci/jep/pull/67 A friendly reminder from one of the JEP Editors, please keep the discussion on this mailing list thread about the document. At this stage of the

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

Hello everyone, Sorry for the time it took to get back here. I think I finally addressed all comments. https://github.com/batmat/jep/pull/1 is ready for another round of comments. I hope that no big thing surfaces again, though obviously there will be issues discovered later, but I feel like we

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

On Fri, Mar 16, 2018 at 4:20 PM, Baptiste Mathus wrote: > yes, users should still backup, JENKINS-49406 is *not* a backup system True, though users will try to treat it as one. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

@Jesse The alternative I had considered too was to just have multiple volumes. But I agree having only one is also more inlined with Essentials philosophy, having only one volume to actually backup (because yes, users should still backup, JENKINS-49406 is *not* a backup system) is simpler. @James

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

On Thu, Mar 15, 2018 at 12:27 PM, R. Tyler Croy wrote: > I > assume that it "just works" and there's no quality concerns we should have > from > a non-standard placement of data on disk? Any obvious problems would have been reported long ago. (I remember some fixes

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

On Wed, Mar 14, 2018 at 1:55 PM, R. Tyler Croy wrote: > core and plugin upgrades can result in > modification of config.xml and other object-serialized-files on disk when an > upgrade occurs. Does happen, but rarely. In most cases, format changes take effect on disk only

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

Where are logs stored (temporarily for the main log as I assume (wrongly) some logstash pump type service)? Both access logs (these should be configured OOTB but are not as of today), and Jenkins logs, and any custom logs (currently $JENKINS_HOME/logs/? I do not think these should be "lost"

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

(replies inline) On Thu, 15 Mar 2018, Baptiste Mathus wrote: > I thought I'd start a dedicated email here about that part after some > feedback I got in https://github.com/batmat/jep/pull/1. > I know people are very busy so maybe an email is easier for many than > looking at the PR. Thank you

[Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

Hey everyone, I thought I'd start a dedicated email here about that part after some feedback I got in https://github.com/batmat/jep/pull/1. I know people are very busy so maybe an email is easier for many than looking at the PR. So the one the ideas I have for Essentials' data snapshotting

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

(replies inline) On Wed, 14 Mar 2018, Baptiste Mathus wrote: > Hello everyone, > > For Jenkins Essentials > , one critical > requirement is to be able to upgrade, and hence rollback in an automated > manner. > So, as we are committed to an

[JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

Hello everyone, For Jenkins Essentials , one critical requirement is to be able to upgrade, and hence rollback in an automated manner. So, as we are committed to an open design process,