Jenkins Overview, Continuous Integration, and System Requirements
Jenkins is a software that allows continuous integration. Jenkins will be installed on the server where the central build will be taken place. The following steps demonstrate a very simple workflow of how Jenkins works.
Developers check their source code.
Jenkins will pick up the changed source code and trigger a build and run any tests if required.
The build output will be available in the Jenkins dashboards. Automatic notifications can also be sent back to the developer.
Along with Jenkins, sometimes, one might also see the association of Hudson. Hudson is a very popular and an open-source Java-based continuous integration tool developed by Sun Microsystems which was later acquired by Oracle. After the acquisition of Sun by the Oracle, a fork was created from the Hudson source code, which will be brought about the introduction of Jenkins.
Continuous Integration is a development practice that requires developers to integrate code into a shared repository at regular intervals. This concept was meant to remove all the problems for finding a later occurrence of issues in the build lifecycle. Continuous integration which requires all the developers to have frequent builds. The common practice to be done is whenever a code commit occurs, a build has to be triggered.
JDK: JDK 1.5 or above.
Memory: 2 GB RAM (recommended).
Disk Space: No minimum requirement. Note that since all the builds will be stored on the Jenkins machines, it has to be ensured that all the sufficient disk space will be available for build storage.
Operating System Version: Jenkins can be installed on the Windows, Ubuntu / Debian, Red Hat / Fedora? CentOS, Mac OS X, openSUSE, FreeBSD, OpenBSD, Gentoo.
Java Container: The WAR file can be run in any container that supports Servlet 2.4/JSP 2.0 0r later. (An example is Tomcat 5).
Visit our website http://mavensoft.com/our-blog/ regularly for Latest Azure Blog Posts