1.

Name three steps or stages a typical Jenkins pipeline might include.

Answer»

Jenkins pipeline is configured to build a project by extracting it from source CODE and then ensure that the build goes through different stages like unit, performance, and user acceptance testing. Once every stage is successful, it ALSO facilitates deployment to an application server. So overall if we talk about different stages any project goes through can be classified into three broad categories 

  • Build -This stage ensures code EXTRACTED from code repository for build purpose and in case of any failure, developers come to know the reason for build failure. This is a very critical stage in build pipeline and SUBSEQUENT stages will be triggered only when the project exits this stage successfully.
  • Test - This stage ensures the build is unit /performance/user tested so the issue can be caught at an EARLY stage only.
  • Deploy - This stage took care of deployment request once testing is successful It is the last stage in the pipeline.

The above stage can be further divided into smaller sections which help us in understanding the importance of three primary stages of Jenkins pipeline:

  • Pull the code from source repository using the proper plug-in. for GIT source code we can utilize GIT plugin and so on.
  • Once the code extracted ensure to compile the code using compatible compiler library like Maven Plugin for Java code.
  • The conformation with coding standard is also well supported by some of the plugins available in Jenkins. We can use the Checkstyle plugin for the same.
  • The Code health check-up is also well supported by different tools available like SonarQube, PMD or FindBugs.
  • Incorporating groovy syntax we can get manual sign off from Business users easily.
  • We can run different tests to measure application load performance.
  • It also helps is packaging application in a form we called ready to deploy stage. For example, the WAR format supported for JAVA web application project, etc.
  • It also facilitates deployment of binary to artifacts repository like Nexus.
  • It also helps in storing most of the reports for future reference.


Discussion

No Comment Found