Introduction:
Continuous Integration is the good practices used in software engineering.These good practices aim at checking that a source code modification does not lead to a regression on the developing software application. This checking is usually performed on a different machine than your development one (this machine is called an integration server); and this checking is carried out rather frequently, and so it's called Continuous Integration.
Jenkins is an open source and java based continuous integration tool. Jenkins enables teams to focus on their work by automating the build, artifact management and deployment processes. Jenkins can track metadata about builds, including the most recent failed and successful builds. It keeps build history and can provide console output. The console output of the build can be helpful in determining if a failure is due to the code or a mis-configured build server.
Jenkins -Workflow:
Installation:
Download Jenkins war file from http://jenkins-ci.org/
You can start Jenkins in two ways: using command line and deploying war as a application in weblogic server
using command line:
open terminal and go to the download location and type the following command to start the jenkins
nohup java -jar jenkins.war &
after few seconds, jenkins will started
open browser and enter the following url, it opens jenkins home page http://<hostname>:/8080
using weblogic server:
start weblogic server and login. Click on Deployment in the Domain structure. Click on Install button.
Continuous Integration is the good practices used in software engineering.These good practices aim at checking that a source code modification does not lead to a regression on the developing software application. This checking is usually performed on a different machine than your development one (this machine is called an integration server); and this checking is carried out rather frequently, and so it's called Continuous Integration.
Jenkins is an open source and java based continuous integration tool. Jenkins enables teams to focus on their work by automating the build, artifact management and deployment processes. Jenkins can track metadata about builds, including the most recent failed and successful builds. It keeps build history and can provide console output. The console output of the build can be helpful in determining if a failure is due to the code or a mis-configured build server.
Jenkins -Workflow:
Download Jenkins war file from http://jenkins-ci.org/
You can start Jenkins in two ways: using command line and deploying war as a application in weblogic server
using command line:
open terminal and go to the download location and type the following command to start the jenkins
nohup java -jar jenkins.war &
after few seconds, jenkins will started
open browser and enter the following url, it opens jenkins home page http://<hostname>:/8080
start weblogic server and login. Click on Deployment in the Domain structure. Click on Install button.
click on upload your file(s)
select Jenkins.war file
select Install this deployment as an application
click on Finish.
open following link in the browser http://localhost:7001/jenkins/
Hello Vishnu,
ReplyDeleteThanks for the post, I did the same way but while accessing the jenkins from admin server/SOA server, I am getting error message in browser as "This site can’t be reached". what would be the possible reasons for it.
PS:- Deployment was done without any errors and I am using jenkins 1.651.3 WebLogic Server Version: 10.3.6.0, please let me know.
TIA.
Hi Sai
DeleteMay I know how did you resolve this ? I am also unable to access after installing jenkins as an applicaiton(.war file) in weblogic