Here I will show you how to create and build jobs in Jenkins. As a prerequisite please read Configuring JDK, GIT and Maven
Already have Jenkins setup in Windows
Already have Jenkins configured with JDK, GIT and Maven
Already have sample java project in your Git repository (either in local or remote repository)
Continue reading “Creating and Building Jobs in Jenkins”
Here I will show you how to configure Jenkins with JDK, GIT and Maven installations. If you need to know setup of Jenkins then please read https://www.jeejava.com/jenkins-setup-in-windows/
Continue reading “Manage Jenkins – Configuring JDK, GIT and Maven”
Jenkins is the leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
- Jenkins is a self-contained Java-based program, ready to run out-of-the-box, with packages for Windows, Mac OS X and other Unix-like operating systems.
- Jenkins can be easily set up and configured via its web interface, which includes on-the-fly error checks and built-in help.
- As an extensible automation server, Jenkins can be used as a simple CI server or turned into the continuous delivery hub for any project.
- With hundreds of plugins in the Update Center, Jenkins integrates with practically every tool in the continuous integration and continuous delivery toolchain.
- Jenkins can be extended via its plugin architecture, providing nearly infinite possibilities for what Jenkins can do.
- Jenkins can easily distribute work across multiple machines, helping drive builds, tests and deployments across multiple platforms faster.
Continue reading “Jenkins Setup in Windows”
I’ve moved some of my projects from SVN to GIT. In Jenkins, builds are working fine but when I try to release, I get the following stack trace
Waiting for Jenkins to finish collecting data
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project hello_world_app: An error is occurred in the checkin process: Exception while executing SCM command. Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref -> [Help 1]
[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.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I think this is a common issue sometimes occur when we try to release a project in Jenkins though the project itself may be successfully built when we run the build using link “Build Now”.
For example, you have the project in GIT repository and there you have branches like “develop” and “master”. When you want to release the project for deploying on Dev, SIT and UAT, you would like to build and release from “develop’ branch, and when you want the project for production release then you would like to build and release from “master” branch. Therefore, you want to click on “Perform maven release” in Jenkins to release an artifact for the project either from “develop” or “master” branch and you may face the error similar to the following
“Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref”
Continue reading “Jenkins: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref”
This tutorial will show you how to deploy both war and jar file from an web application using maven in Jenkins. By default when we build the web project in Jenkins then war file gets uploaded into nexus but not jar file.
Sometimes we need to upload both war and jar files from an web application using maven because some other standalone project needs to include the jar file of the web application and some another web project may need to include the war file of the web application. Hence we require to upload both war and jar files into Nexus. Continue reading “Deploy both war and jar files into Nexus using maven in Jenkins”