[
https://issues.jenkins-ci.org/browse/JENKINS-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159384#comment-159384
]
Robert Kahlert commented on JENKINS-12125:
------------------------------------------
I am with Samuel on this one. Just making the backup name editable, so that
people can take out the $DATE part would be sufficient.
I can check it into SVN myself, that's not the issue.
> Push backups in remote git repository (or any other SCM)
> --------------------------------------------------------
>
> Key: JENKINS-12125
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12125
> Project: Jenkins
> Issue Type: New Feature
> Components: thinBackup
> Reporter: Samuel Stirtzel
> Assignee: Thomas Fürer
> Priority: Minor
>
> Hi,
> it would be nice if the backup could be pushed in a remote SCM (e.g. in my
> configuration: git).
> Summarized it could be done like this:
> * Check if the target directory is in a SCM (for git: check if .git directory
> is present)
> * Automatic backup
> * Stage the backup files and commit
> * Push to origin (the remote repository)
> Alternative to that, let the user run a shell script after backups.
> Edit:
> When stored in a SCM the naming scheme is disturbing, as the files should get
> overwritten each time a backup is running.
> So if thinBackup creates "backups/FULL-2011-12-01_12-15/" and
> "backups/FULL-2011-12-08_12-15/" it is not possible to directly put them in a
> SCM without moving files around or it will create duplicate content.
> --
> Regards
> Samuel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
