Jenkins Contd

• We use Jenkins to create CI/CD pipelines which generally starts from the version control system like git.
• We need to clone the code and start building a package.
• Building a package depends on the language of your application.
• Cloning the code from git
  • git url
  • credentials (username/password or ssh key)
  • branch
• Lets consider the following two java opensource applications
  • spring pet clinic:
    • developed in java
    • requires jdk 11
    • repo url: Refer Here
    • Lets clone
      
      
  • Open MRS:
    • developed in Java
    • This is open medical record system
    • repo url: Refer Here
• Jenkins will provide User Interfaces to help us increase the pace of creating cicd pipelines. These User Interfaces are added to jenkins by a concept called as plugins.
• While installing jenkins we have executed install plugins
• The UI below is from a plugin called as git plugin
  
  
  
• Lets clone openmrs
  
  
• Lets consider the following .net opensource application and clone it
• nop commerce
• default branch: develop
• Create a new jenkins job to clone the code Refer Here for repo url
  
  
• Clone the odoo Refer Here with default branch as v15.0
  
• As discussed in the session, We can clone code from git repo (public or private).
• Now we should be able
  • to create the package/build from the cloned code.
  • unit test the code and show the test results
• The above steps change from technology (java, .net, python, nodejs)
• To understand the build system and the unit test lets start by learning a tool called as maven, which helps in build a package for java based languages.