DevOps.... CI/CD

Every software development needs coding; without it, nothing can be developed. The quality of software depend on the way developer write code. It's an essential part of the system and the behavior of the system depends on it.  A small mistake in coding may make software vulnerable and unstable. Quality engineering works hard to find bugs to avoid potential problems with the software. They spend numerous hours and put tremendous effort into finding any problems with the software and reporting it to the developers. Cost of fixing the defects at various level. The Cost of fixing defects at latter stage increases exponentially, hence, you need more hours of QA Engineers and Developers to fix and run the entire release cycle again. If we can save some amount of time and effort from above, we can utilise resources in more productive way. Can we make sure code is better written, tightly secure, having no potential bug and right libraries ...

In this post i am going to talk about maven build troubleshooting, Here is the list few maven error and its troubleshooting.  This is the part 2 of the Troubleshooting tips. concurrent.ExecutionException If you see following type of error in your release build. [ERROR] java.util.concurrent.ExecutionException: java.lang.NullPointerException   [ERROR]     [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.     [ERROR] Re-run Maven using the -X switch to enable full debug logging. Solution Your build job is having parellel execution, Please contact Release team to "-T -1C" get removed from the job. Docker image building failed due to Unable to locate package If you see following type of error in non java projects release build. [INFO] [91mE: Unable to locate package [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare (default-cli) on project : Mave...

Docker is very powerful containerization technique, and it is becoming famous in short time. People are adapting and containerizing their applications for deployment. Soon container become very heavy and consume too much of disk space, If you do not delete old images and layers you may soon run out of disk space. Here i am trying to cover the ways to regain the disk space consumed by docker images. Moving docker filesystem to bigger mount point. Usually docker keeps all temporary files related to image building and layers at /var/lib/docker This path is local to the system usually at root partition "/" . You can mount a bigger disk space and move the content of /var/lib/docker to the new mount location and make sym link.  This way even docker images occupy space, will not affect  your system as it will be using some other mount location. Remove Old docker images Here are few ways to remove old and unused docker images Removing stopped contai...

docker-maven-plugin is the great plugin provided by spotify to build docker image during maven build. There is very strange error or behaviour I have seen during the image creation. Plugin expects that image which Dockerfile is pulling needs to be passed with username and password, which should not an essential parameter as most of the images does not need any auth to be downloaded.  You may see this error [INFO] Building image your-application:0.0.3 Step 1 : FROM ubunt:latest [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] your-application..................................... FAILUER [ 3.619 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 39.938 s (Wall Clock) [INFO] Finished at: 2016-06-25T16:26:06+00:00 [INFO] Final Memory: 65M/1216M [INF...

In this post i am going to talk about maven build troubleshooting, Here is the list few maven error and its troubleshooting. Tag Already exist If you see following type of error in your release build after the perform step [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project : Unable to tag SCM [ERROR] Provider message: [ERROR] The git-tag command failed. [ERROR] Command output: [ERROR] fatal: tag '<some tag>' already exists

Git is distributes system, the beauty of the git make is more robust and easy to recover from any last known good working copy. However, You can not always rely on such copy and you will definitely need proper backup solution to deal with such situation. There are many ways to take backup of git repositories. I am listing few here. You can directly take a tar of the git repo directory as it has the whole bare contents of the repo on server. There is a slight possibility that somebody may be working on repo while taking backup. The following command will give you the bare clone of repo (just like it is in server), then you can take a tar of the location where you have cloned without any issue. git clone --bare {your backup local repo} {new location where you want to clone}

If system throws "too many open files" error or something like following during build/compilation [INFO] java.io.FileNotFoundException: (Too many open files) This means limit to open files for the user or system has been exceeded. You can check the limit by running following command ulimit -a Solution -> open file common-session sudo vi /etc/pam.d/common-session Add following entry in the file session required        pam_limits.so open file limits.conf sudo vi /etc/security/limits.conf make sure both soft and hard limits are set to larger number (as per your need) *                soft    nofile          500240 *                hard    nofile          500240 Logout and login and run command again ullimit -a You will see the new limit number.

I was trying to compile and install thrift from  https://github.com/apache/thrift . While compiling the thrift for 6 and 8 version i faced few errors and had to spend lot of time fixing it   (Including searching various solutions on Net). Let me  detail out few error and solution for it. Missing thrifty.h  src/thriftl.ll:50:21: fatal error: thrifty.h: No such file or directory compilation terminated. make[3]: *** [libparse_a-thriftl.o] Error 1 make[3]: Leaving directory `/home/abc/thrift/compiler/cpp' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/abc/thrift/compiler/cpp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/abc/thrift' make: *** [all] Error 2 Solution -> You will have thrifty.hh file instead of thrifty.h. Location of file would be  ./compiler/cpp/thrifty.hh  cp ./compiler/cpp/thrifty.hh ./compiler/cpp/thrifty.h and start your compilation again, It should work. Non stat...