The Best CI Tool :: Jenkins

#ContinuousIntegration #CI #Jenkins #CITools #OpenSource #VCS #Testing #Github

JENKINS is a Continuous Integration (CI) server or tool which is written in java. It provides Continuous Integration services for software development. Its an “Open source community with many plugins & flexibility as an automation platform. Also, it is a free software to download and install. To pass your code into production as soon as one check in the code into VCS without anybody’s involvement is what Jenkins does. It Builds  code, performs test cases, Builds  artifacts and publishes it into the production. Jenkins can help one to execute a build on every change in version control system, git/subversion. It is a good tool for automating the execution of one’s build script. It can also build periodically so one will know that the build works even when the source code hasn’t changed. The build script has to do all steps needed, compile, test, package, acceptance tests and so forth. The build script must be possible to execute from a command line.

Some advantages of using Jenkins::
– Building/testing software projects continuously. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project. The automated, continuous build increases the productivity.
– It is easy to install.
Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine.
• It has 1000+ plugins to ease your work.
• It is built with Java and hence, it is portable to all the major platforms.
• It is also used for deployment of released artifact with custom scripts.
• It provides continuous integration pipeline support for establishing software development life cycle work flow.
• It also provides support for scheduled builds & automation test execution.
• One can configure Jenkins to pull code from a version control server like GitHub, BitBucket etc. whenever a commit is made.
• Whenever a commit is made to the source code, in the shared repository, like GitHub, Jenkins server will pull that code and trigger a build.
• Once it is compiled, Jenkins will then deploy that build application on the test servers for testing.

Share This :

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.