Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Overview

Jenkins, an open source CI tool is used to run build for Connect project for different profiles and deploy code to different application servers. 

Configuration

  1. Nightly build is configured to get fresh source code from Git Repository, compile, build and deploy to application servers. We are using JBoss and embedded wildfly application servers to do deployments. Build is configured to run every day at midnight. 
  2. We use Maven, as build tool to build the code, run different goals and specific plugins. 
  3. By default build will run profiles which are configured to run when no profiles are passed but we can particular profiles - like PD, AD, X12, DR as command line argument to maven command.
  4. Maven builds are highly configurable and we can pass different pom file and configure the path, JVM options and settings file to build the profile.  
  5. We currently keep 10 last builds for history purpose.
  6. We also publish analysis results for findbugs and dependency-check source code quality checks. 
  7. We are using shell commands for:
    1. For using Git to get fresh repo code ( git checkout CONNECT, git pull, git clean -dfx ).
    2. For cleaning up earlier deployed directories ( rm -rf $WORKSPACE/.repository/*, cp ../settings.xml ).
    3. For connecting to JBoss application server machine and deploying source code for that application server.
    4. For calling other scripts in order to clean up, start, undeploy and stop servers.
  8. An experimental plugin called "Warnings Next Generation" to aggregate Findbugs, Sonar, Java, and Checkstyle issues into a single viewable report on the nightly jenkins job.      


Issues and Resolutions

IssueResolutionTicket
JBoss ear not deployingProblem was that, it was pointing to wrong java version, It was using 1.6 java version instead of 1.7 version and JAVA_HOME was not set to correct java version. In order to fix this problem, we changed .bashrc file under /home/jenkins directory to point to correct java versionFHAC-481  
Dependency check failingIt was missing advance settings information which was mentioned for findbugs plugin to run and there is new profile which is added called SCA and by adding that profile, it runs dependency check and source code analysis pluginsNo ticket, this was a secondary issue that was discovered and resolved as part of FHAC-481
  • No labels