Here at ClearHub we specialise in sourcing the right contractors for organisations looking to improve their software delivery, and we have clients that need your Git expertise!
We currently have unfilled opportunities with some industry leading clients, working on cutting edge projects that require highly skilled contractors.
So if you have experience working with Git and other version control systems, we’d love to hear from you.
Rates depend on your experience, skill, location and client budget, but we work with all parties involved to make sure everyone is happy. We have long ongoing relationships with contractors and clients alike.
Nobody wants to be stuck in a job with legacy tech or boring work. Our clients need help upgrading to next-generation solutions. If you’re not a fan of sitting still, then we’ve definitely got the right role for you!
Depending on the project support might consist of technical support (for the Atlassian stack) or simply HR support – whatever it is, our team are here to help throughout the duration of your contract.
Our clients often want a contractor whose going to come in and oversee the whole migration process, from preparation through to mentoring the team on their new tool. We’ve outlined what a client may require from a typical SVN to Git migration.
The first step will be making sure your client and their systems are prepared for the migration. This could include downloading a utility script, mounting a case-sensitive file system and mapping author information from SVN to Git.
You’ll then have to import the contents of the SVN repository into a Git repository. Depending on whether you’ve planned a one-way sync or are going to be committing to both Git and SVN, advanced actions may be required at this stage, such as cleaning the new Git repository.
By synchronising the Git repository with new commits in the original SVN repository, you can allow a period where you the client can continue to use SVN but also experiment with Git. They may want you to start providing some extra support and training as they begin to experiment.
At this stage, you will be able to set up a hosted repository such as Bitbucket, so that the converted Git repository can be shared with the development team. They can continue synchronising with the SVN repository until you’re happy that the whole team is ready to migrate.
Once everyone is ready, you can make the switch. At this stage you can freeze the SVN repository at whatever state its in and any future commits can be made in Git and shared via Bitbucket.
At ClearHub, we’re more than just a one trick pony.
We cater to all sort of clients, with a variety of software development projects, specialising in DevOps, Agile and the Atlassian stack.
If you have skills you think we may be interested in, send us your CV and we’ll get back to you with any projects we think you’d be a good match for!