Please enable JavaScript.

Coggle requires JavaScript to display documents.

Continuous Integration (NEXUS (UPLOAD THE BUILD) (nexus> bin> …

- - - - COMPILE CODE = CONVERT TO CLASS FILES
        
        WELCOME.CLASS
        
        O/P WELCOME
        
        MACHINE READABLE BINARY FORMAT
        
        for multiple java files (100 java files)
        
        javac *.java
      - PAIN AREAS
        
        TIME CONSUMING & TYPICAL
        
        javac #### for each java file
        
        pull libraries for code
        
        UNIT TEST CASE level testing manually - LONG TIME
        
        O/P BUNDLE CREATION (package) & COPY TO DIFF. ENV.
        
        REVIEW
        
        CODE REVIEW
        
        CODE COVERAGE
        
        TEST RESULTS
        
        VULNERABILITY
        
        CHECK STYLE
        
        performance issue
        
        memory leakages
      - JAVAC WELCOME.JAVA
  - - - RESOURCES (NON COMPILED CODE)
      - JAVA
    - - basic files in any application = src, pom.xml
      - it has main & test folders (tree command)
        
        test = Junit test cases, mockeries
        
        Main is actual business code, test is for testing main code
      - mvn --help
    - - EACH MODULE HAS ITS OWN POM.XML
      - PARENT TYPE "WAR" NOT "JAR"
      - O/P OF BUILD IS WAR
      - multiple modules in single application
        
        Now
        
        Services
        
        Microservices
        
        Multiple Components
        
        Multiple Modules
        
        Monolithic Application
        
        Each module independent of other
      - maven directly calls all pom.xml
      - Each module will have its own target generated by mvn
- - - - COLLECT RESOURCES
      - COMPILE SRC. CODE
      - TEST CODE
      - BUNDLE CODE & copy in local repo (NON EDITABLE FILES)
      - KEEP/upload BUNDLE IN CENTRALIZED REPO (nexus)
      - generate CODE REVIEW REPORT
      - generate CODE COVERAGE REPORT
      - DEPLOY APPLICATION IN WEB SERVERS (tomcat)
      - PROPER DIRECTORY STRUCTURE for application
    - - jdk
      - maven utility
      - centralized repo (or maven repo online)
      - sourcecode
      - sonarqube
      - nexus repo / or Jfrog Artifactory server
  - - - JAVA --VERSION
    - - MVN --VERSION
      - MVN --HELP
      - POM.XML (MAVEN READS THIS)
        
        HTML (PRE-DEFINED TAGS)
        
        XML (USER DEFINED TAGS)
        
        XML CONTAINS DATA
        
        DATA STORED WITHIN TAGS
        
        TO UNDERSTAND TAGS WE HAVE SCHEMAS B/W 2 SYSTEMS
        
        Parent Project, Child Dependencies, Sub Child, Standalone Tags
        
        !-- to uncomment
        
        MAVEN DEFINED XML FILE add dependencies
        
        mvn -f pom.xml deploy = looks for pom.xml in current directory
        
        CONTAINS ALL DEPENDENCIES OF SRC. CODE
        
        CONTAINS DATA OF SRC. CODE TO BUILD
        
        ARTIFACT INFO
        
        REPO NAMES
        
        DEPENDENCIES
        
        PLUGINS - COBERTURA, JACOCO, TOMCAT, SUREFIRE, JAR
        
        PROFILES
        
        developer gives pom.xml
        
        eclipse creates (Maven Project) - Project Name, Src, Pom.XML
      - O/P OF BUILD = BUNDLE = ARTIFACT
    - - RESOURCES
      - COMPILE
      - VALIDATE (checks build syntax)Success/Fail
      - TEST
      - PACKAGE (jar, tar, war)
      - DEPLOY
      - INSTALL (.m2 local repo created - store all downloaded file jar, war etc.)
      - MVN CLEAN (mvn clean install)
    - - .M2 FILE CONTAINS ALL DEPENDENCIES DOWNLOADED AS PER POM.XML
      - mvn -f pom.xml -P spring-deploy clean deploy (only this module gets executed)
- - - - Hosted
      - Proxy
      - Virtual
      - Roles
        
        Users
        
        Privileges