Jenkins is an open source automation tool written in Java with plugins built for Continuous Integration purpose. Jenkins is used to build and test your software projects continuously making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. It also allows you to continuously deliver your software by integrating with a large number of testing and deployment technologies.
If there is one tool that the vast majority of DevOps teams have deployed, it is Jenkins. There are other tools, but Jenkins is the “Got DevOps?” standard. If Jenkins has a problem, it is one of abundance. The Jenkins plugin category is an embarrassment of riches: As many as 1,500 different plugins are available for Jenkins.
Certainly, Jenkins has taken steps to make plugin selection easier for its users, but the first thing every new user asks is, “Which plugins do I need?” Short answer: As few as possible. Especially at first. Start with a source code management (SCM) repository plugin (GitHub, BitBucket or Local Git, for example) and another plugin for builds (Gradle or Maven, for example). More can be added later, but starting light keeps the build/test environment simple and manageable, and doesn’t load down Jenkins with unnecessary plugins.
Jenkins 2.0 also includes Jenkins Pipeline and a friendlier interface (Blue Ocean). Managed Jenkins and other enterprise features are available from CloudBees Jenkins Enterprise.
Access the URL : http://Ip-Address-of-your-Server:8080