Just do ... Git

My latest task at the company is to support (and carry out) the migration of our codebase (significant amount of code in ~100+  software modules/projects) from CVS to Git.

This is expected to go a seamless as possible without affecting the current work of the whole department (30+ devs) so I needed a whole arsenal to tips an tricks to do this, but it seems that things are starting to take shape.

Together with this migration we also decided to move from legacy Hudson to Jenkins, and from legacy file-share based artifact repository to Nexus...just to keep things interesting...

...so the new Year comes with new gear(s) ... Git and his friends... beginning of a new era at the company... and who knows ...maybe at some point we might go wild and switch to Maven or Gradle :)
...but until than the trusty Ant and Ivy will keep things flowing.

Upgrading the technology stack

If you develop software chances are that eventually your state of the art technology stack will fall behind...something that once was great stuff becomes old and outdated.

Using always cutting edge technology is simply impossible in a bigger company and bigger projects...as with every technology stack update you introduce regression...and since the customers have no direct benefit from this...eventually the company will cut the effort for staying up to date.

Something that works should not be changed unless there is a good reason for it.

And so we end up using Ant+Ivy and CVS and Java 8 in 2019...where everyone is using Maven and Gradle and Git and Java 11...and you have to argue constantly why...

Upgrading the technology stack of a department is not that simple...we have to move slowly and cautiously...and we will get there...and products will not suffer.

..and everyone will be happy...except those who will not.