Monday, August 19, 2013

Tip : Setting up Git Jenkins integration on windows box

If you have ever tried setting up git as a version control system in a Jenkins installation on a windows box you would have faced an error message ssh key not available.

The reason behind this issue is that if you are using git with ssh protocol it tries to use your private key to perform git operations over ssh protocol & the location it expects is the .ssh folder at home directory of user. To fix this issue you have to create a HOME environment variable and point to your home directory where your .ssh folder exists after that restart Jenkins & now it should work fine.

Thursday, August 8, 2013

Linux Utility to manage login to systems

One of the problem I used to have as build & release engineer is to manage login to huge number of boxes through my Linux system. At the scale of 5-10 machine it's a not a big problem but once you have close to 100+ boxes then it is not humanly possible to remember the ip's of those boxes.
The usual approach for this problem is to maintain a reference file, from where you map machine name with the ip & find the ip of the box from this file, but again after some time this solution seems to be not that efficient. Another solution is to have a DNS server where you can store such mappings & then you can access these machines using their names only, this is the idle solution but what if you don't have DNS server also still you have to execute the ssh command 'ssh user@machine".

I developed a simple solution for this problem, I created a utility script, this script takes machine name as an argument & then we have multiple conditions statements which checks which ssh command to be executed for the machine name.

if [ "mc1" == $1 ]; then
    ssh user@
elif [ "mc2" == $1 ]; then
    ssh user@
elif [ "mc3" == $1 ]; then
    ssh user@

This solution worked really well for me as now I'm saved from executing whole ssh command, also for machine name I've followed a convention i.e _ for example the entry for a machine for release environment that is hosting an application catalog the machine name would be release_catalog, similarly dev_catalog, staging_catalog, pt_catalog.. so you don't have to remember machine names as well :).