Re: Jenkins putting '$' characters in file/folder names, breaking automatic backups

2014-04-10 Thread Richard Bywater
According to http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx, $ is a perfectly valid character for naming files & directories. And since Java uses $ to represent inner classes in .class files then this helps prove that theory. I'm not sure what the "Location is unavi

Re: Jenkins putting '$' characters in file/folder names, breaking automatic backups

2014-04-10 Thread Daniel Beck
On 10.04.2014, at 15:56, Scott Evans wrote: > Anyone know why this may be occurring and what I can do to resolve this? It's a Maven job. AFAICT, they've always (or at least since 2009) worked like this to store artifacts and logs separate for each module, see e.g. https://github.com/jenkinsci

Re: Jenkins putting '$' characters in file/folder names, breaking automatic backups

2014-04-10 Thread Scott Evans
To ???: A few quick thoughts (since I don't have access to your machine and environment): - You said you ran the command-line job on the Jenkins server itself? Is this the same physical box where the build ran that's causing problems? Most people are set up with a Jenkins server and then agent m

Re: Backups

2013-10-31 Thread Jared Griffith
Thanks I just did the rsync thing just to make sure I got everything I needed. On Wed, Oct 30, 2013 at 10:38 AM, Thomas Fürer wrote: > just look at thin-backup. will backup all relevant data from your > workspace in regular basis. > > Am 30.10.2013 00:30, schrieb Jared Griffith: > > I was wonder

Re: Backups

2013-10-30 Thread Thomas Fürer
just look at thin-backup. will backup all relevant data from your workspace in regular basis. Am 30.10.2013 00:30, schrieb Jared Griffith: > I was wondering what files are necessary to back up a Jenkins master > instance? I don't really think it's necessary to backup the workspace > and all that,

RE: Backups

2013-10-30 Thread Matthew.Webber
> > where the rsync_exclude_filters.txt file contains this: > > (snipped) > > I would exclude workspace (as in vast majority of caseses this is > dowanloaded or generated), but keep builds as there might be important > artifacts there (if they are not important you should not store them in > first

Re: Backups

2013-10-30 Thread Maciej Jaros
matthew.web...@diamond.ac.uk (2013-10-30 10:17): I have a job that runs each night and does an rsync of $JENKINS_HOME, skipping the history. Specifically, I use this command: rsync --verbose --itemize-changes --archive --omit-dir-times --whole-file --stats --exclude-from=/path/to/jenkins_home/

RE: Backups

2013-10-30 Thread Matthew.Webber
/*/svnexternals.txt *.bak *~ Obviously, this does not keep any history. Hope that helps Matthew === From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jared Griffith Sent: 29 October 2013 23:31 To: jenkinsci-users@googlegroups.com Subject: Backups I was wondering

Re: Backups

2013-10-29 Thread Jared Griffith
I was thinking the rsync thing, but I really don't want to sync the 16 Gb workspace directory. I wasn't sure if there would be an issue with that. Maybe this groovy script will work fro what I want. On Tue, Oct 29, 2013 at 5:58 PM, Ingo Richter wrote: > Hey, > > I have a simple groovy script t

Re: Backups

2013-10-29 Thread Ingo Richter
Hey, I have a simple groovy script that creates a backup on our master machine. I have a backup job that will execute this groovy script. The script itself creates a zip file with a couple of config files. I've used the backup to restore our build machines in very little time last week. Thanks t

Re: Backups

2013-10-29 Thread krishna chaitanya kurnala
Hi Jared The easiest way is to maintain a copy of .jenkins folder on diff server and have a rsync command run with cron or something to keep them in sync, take a look at the backup plugins as well. thanks Krishna Krishna Chaitanya On Tue, Oct 29, 2013 at 4:30 PM, Jared Griffith wrote: > I was

Backups

2013-10-29 Thread Jared Griffith
I was wondering what files are necessary to back up a Jenkins master instance? I don't really think it's necessary to backup the workspace and all that, I just want what is necessary in case the server goes boom and I have to put it up on another server. Yeah, it would be nice to have all of the