Version control for version control?

I was overseeing branching and merging throughout the last release at my company, and a number of times had to modify our Subversion pre-commit hooks to enforce different requirements on check-in comments and such. I was a bit nervous every time I was editing those files, because (a) they’re part of a live production system, albeit only used internally (and we’re not a huge organization), and (b) they’re not under version control themselves.

I’m curious what sort of fail-safes people have in place on their version control infrastructure. Daily backups? “Meta” version control? I suppose the former is in place here as part of the backup of the whole repository. And the latter would be useful as the complexity of check-in requirements grows…

  • How to structure source control repository for a platform with iOS, Android, Web apps and Java backend?
  • Should I commit or ignore Terraform local module symlinks?
  • Git merge & adding change id
  • How to make a commit, or a change permanently local
  • How can I merge my “ready” changes to another branch without commiting the “non-ready” changes?
  • A Git Source Control strategy for a live Sitecore website
  • What to do about a 11000 lines C++ source file?
  • Modified files don't stay staged after stash save and stash pop
  • Is there a way to purge some files from the history of git?
  • hiding part of a git repo from untrusted users
  • How best to handle Git Deployment For multiple web servers
  • Migrating a large SVN repo to git
  • 4 Solutions collect form web for “Version control for version control?”

    Natch – the version-control and any other infrastructure code is also under version-control but I would use a separate project from any development project.

    I prefer a searchable wiki or similar knowledge-base repository to clogging up your bug-tracking system with things like VCS config.

    Most importantly, make sure that the documentation is kept up to date – in my experience, people are vastly better at keeping code docs up to date than admin docs. This may have been the individuals concerned . One thing that is often overlooked is, if systems are configured according to standard Unix Practices or similar philosophy, that implies a body of knowledge about locations that may not be familiar to an OS/X or Windows programmer, faced with suddenly fixing a broken script. Without being condescending, make sure basic assumptions about location and interdependency are documented.

    You should document all “setup” configuration for all your tools and these documents should be checked into version control. For tools with text file configurations which allow comments, you could just checkin the config file. But for tools that require using the interface, you should have a full document with images of the dialog boxes showing what choices are chosen.

    Most importantly though, these documents should say WHY you have set the values chosen (when not taking the default).

    Second, as backup, the same documents should be included in your bug tracking software under a “How do I setup the version control software?” bug. (The bug tracking database is located on a different physical server, right?)

    Third, all of this should be backed-up off-site. I’m sure there question on SO about backup strategies.

    What’s wrong with using the same version control repository for the commit hooks and other configuration files? That’s how I’ve handled it in the past when I’ve been responsible for a project’s configuration management.

    You should also back up your svn repository. That way if the repository itself becomes corrupted or the server catches fire or something, you can recover both your project and the svn control files.

    If you have build scripts that are doing this (such as Nant) then you could be checking in those.

    Git Baby is a git and github fan, let's start git clone.