+91 700 483 5930   +91 810 584 3520    info@scmgalaxy.com
Sign In or Register
Not Registered Yet?

Join Now! It's FREE. Get full access and benefit from this site

Reset My password - Remind Me My username

Remember me
scmGalaxy logo
Rajesh Kumar

Rajesh Kumar


Total, Over 12 years of extensive experience in the Software Configuration Management domain having depth knowledge of DevOps, Continuous Integration and Delivery, Configuration Management, Build and Installer, Release Management and Application Management.

Website URL: http://www.RajeshKumar.xyz Email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Create a subscribe form for your rss feed
Joomla Website with K2 Content
RSS To email using mailchimp
RSS To email using hubspot
RSS to email using phplist
Feed Burner
Bitbucket plugin is designed to offer integration between Bitbucket and Jenkins.

It exposes a single URI endpoint that you can add as a WebHook within each Bitbucket project you wish to integrate with. This single endpoint receives a full data payload from Bitbucket upon push (see their documentation), triggering compatible jobs to build based on changed repository/branch.
Step 1 - Install "Bitbucket Plugin" at your Jenkins
Step 2 - Add a normal Post as Hook to your Bitbucket repository (Settings -> Hooks) and use following url:
and if you have setup authentication on jenkins then URL must be like
https://USERNAME:This email address is being protected from spambots. You need JavaScript enabled to view it.:PORT/bitbucket-hook/
Step 3 - Configure your Jenkins project as follows:
Step 4 - Under build trigger enable Build when a change is pushed to BitBucket
Step 5 - under Source Code Management select GIT; enter your credentials and define Branches to build (like **feature/*)
Note 1 - Make sure to include the slash ('/') on the end of the URL or the hook won't work.
Note 2 - Please read the BitBucket Plugin info page as well https://wiki.jenkins.io/display/JENKINS/BitBucket+Plugin
Reference 1  
Reference 2 - Login issues with Jenkins url

How to configure Sonatype Nexus repository with Maven?

Automatic dependencies is one of the powerful feature of Apache maven and its one of the reason Maven is very popular in developer community. Maven resolve the dependent library from local repository which is again connected with central repository or remote repository. thus we can say that Maven has 3 kinds of repository concept.
1. Local repostory e.g $USER_HOME/.m2
2. Central repostory e.g http://repo.maven.apache.org/maven2/
3. Private repostory e.g Sonatype Nexus, Artifactory, Archiva etc.
The diagram shown below represent how maven resolve the dependendency.
High Level Interaction between Local Repository, Central Repository and Remote Repository.

Dependency Management using Local Repository, Central Repository and Remote Repository.

This is How maven interact with Repository!

This is a diagram which shows the define flow in which maven try to resolve the dependency.

Now, We have understood that Central rrepository is in built but next questions is, How to inform the maven about the location of remote repository? In order to configure maven with remote repostory, in our case SonaType Nexus, we need to configuring host machine setting.xml and projects pom.xml to use your Nexus repos.

Put this in your ~/.m2/settings.xml file. This will configure the credentials to publish to your hosted repos, and will tell your mvn to use your repo as a mirror of central:

And now configure your projects.

If you want only to download dependencies from Nexus, put this in the pom.xml:


Add the following at the end of setting.xml


    <!--make the profile active all the time -->





How can we do the Security Analysys using SonarQube?

For Security Analysy purposes, a source code security analyzer
- examines source code to
- detect and report weaknesses that can lead to security vulnerabilities.

SonarQube Upgrade, Backup and Restore Process

Today I will share the steps to upgrade from the SonarQube version 5.X to SonarQube version 6.X. We have upgrade guide which can be found http://docs.sonarqube.org/display/SONAR/Upgrading but its not complete guide thus I am sharing the steps as follows which can be followed for the production server as well.  As practice shared on the oficial guide that before upgrading to the next major release, you must upgrade to know LTS e.g

Page 1 of 56