Why System Administrators Should Use Revision Control
-
We don't use RC here, even though I've pushed for it since starting. So much wasted energy on "tracking down this version".
Well it's not a version if it has no version number....
-
It's much harder for Windows shops that use the GUI instead of text based controls. Windows, in general, is much harder to revision control than UNIX systems. UNIX being text based is so easy to put under revision control. But Windows, you have to be creative. Unless you are already using tools like Ansible, Chef or Puppet.
-
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
-
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
You definitely need to get GIT running, then.
-
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
That is not system administration. That is standard development.
-
@JaredBusch said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
That is not system administration. That is standard development.
Our development team often goes back and forth between versions, or references one file over and over again making minor tweaks, but keeping every change.
-
@DustinB3403 said in Why System Administrators Should Use Revision Control:
@JaredBusch said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
That is not system administration. That is standard development.
Our development team often goes back and forth between versions, or references one file over and over again making minor tweaks, but keeping every change.
Yup, that's what revision control is for. You have developers who do anything without revision control? Who hired these people?
-
@scottalanmiller said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
@JaredBusch said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
That is not system administration. That is standard development.
Our development team often goes back and forth between versions, or references one file over and over again making minor tweaks, but keeping every change.
Yup, that's what revision control is for. You have developers who do anything without revision control? Who hired these people?
Exactly. Development should alway bne under version control. But the point of my statement was that your issue is not system administration that @scottalanmiller is discussing.
-
@scottalanmiller said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
@JaredBusch said in Why System Administrators Should Use Revision Control:
@DustinB3403 said in Why System Administrators Should Use Revision Control:
Oh I totally agree, but with the digital content we create here, and having 15000 different versions of a near identical file, and watching these guys go back and forth of "which one was one pixel to the left....."
We could really use revision control....
That is not system administration. That is standard development.
Our development team often goes back and forth between versions, or references one file over and over again making minor tweaks, but keeping every change.
Yup, that's what revision control is for. You have developers who do anything without revision control? Who hired these people?
The clown master of course...
-
Revision control is pretty easy today. And so many free options, even hosted ones. GitLab, BitBucket, GitHub or just run your own Subversion server or whatever.
-
Revision control was a huge thing. It's essential anywhere two or more sysadmins are working (real sysadmins, not generalists like me.)
Had a bad experience with it back in the 90s when the German parent company thought they were a special snowflake, and could operate differently than what the internet connections could handle. T1 + transfer engineering drawings = fail, T1 + ship CD + real time software also equals fail. All so they didn't have to maintain two different drawing repositories (even tho the software was able to search many sites.) Noooo, we can't make engineers login to a different site. Silly.
-
With even just one system admin, revision control is nice for just tracking what you've done.
-
That's a nice aspect of systems like Ansible, they basically force good practices like this.
