Do you use git or some othe revision control system as part of your workflow?

in the past, I had done web development so I gained some exposure to the revisioning systems of the day (mainly SVN) and I recently started to use git more as part of my daily workflow. I setup an internal git server(gitlab), which is used for storing configs from some network devices, scripts, source code, package lists from our internal repo servers, and Group Policies. Like so many other things, when you start using it and making it part of a routine, other uses just start magically appearing.

This has been a little harder sell than I thought it would be because my admin colleagues see it as additional work so they aren't completely sold on the merits of keeping information under source control, plus, we don't have any internal policies that require it so it is voluntary.

I know the devs in the crowd are using some form of version control but what about other system admins and network admins, do any of you integrate these types of tools into your day to day operations?

Find more posts tagged with

Comments

Verities

I'm using it for BASH and Python scripts as well as Ansible Playbooks.

blargoe

I have a local install of git that I started using a few months ago for managing changes to my scripts. You're right about other uses coming to mind once it become part of the routine. My department doesn't have a git server yet, but it should be a pretty easy sell.

networker050184

I use gitlab for personal stuff I work on, but we use github enterprise at work. On the networking side specifically we use it for versioning control for scripts, config files, ansible, rancid repo.

alias454

blargoe wrote: »

I have a local install of git that I started using a few months ago for managing changes to my scripts. You're right about other uses coming to mind once it become part of the routine. My department doesn't have a git server yet, but it should be a pretty easy sell.

Gitlab is a really nice setup AFAIC. One of the bigger challenges I have found is trying to round everything up that could/should be under revision control. A lot of this stuff has been the way it is for a decade(or more). While everything is being backed up it isn't easy trying to go back through change mangement systems and correlate the day when a config file changed or something else like it. I mentioned in the first post I also use it to keep track of group policy changes. This took a little bit of doing but I setup some powershell scripts to automatically pull down group policy files once a day and then they get shipped to the gitlab server. This isn't perfect but for a first pass I think it worked out pretty slick. One drawback is I can tell you when but not who since the job runs under a service account. But we can take that and check against the log server to see an audit trail.