ABOUT JENKINS:

1. Jenkins is a server side application that can be used by Developers, QA engineers, DevOps engineers
2. Jenkins is referred to as CI CD CT tool
3. CI → Continuous Integration → This is the process where different sets of code written by different dev teams shall be integrated together for integration testing purposes by Jenkins tool. Actors involved in the CI phase are front-end developers, back-end developers.
4. CD → Continuous Deployment → This is the process where the Jenkins tool shall automatically deploy the unit testing code which has passed the integration tests from Dev server to the QA server and rejects the failed code so that QA team & Dev team are notified about the deployment status and CI testing status. Actors involved in the CD phase are the DevOps team.
5. CT → Continuous Testing → This is the process where the Jenkins tool shall trigger automated tests to execute on the build generated by Jenkins tool using CD and then the passed code shall be deployed to the next env such as UAT env or prod env. Actors involved in the CT phase are QA Engineers.
6. CD → Continuous Delivery → This is the process where the Jenkins tool shall deploy the passed code into the production servers for real uses to access the application. Actors involved in the CD phase are the DevOps team
7. Jenkins workflow is CI → CD → CT → CD

8. Jenkins is built on java
9. Prerequisite for Jenkins: Java JDK v11 or v17 or v21 https://www.jenkins.io/doc/book/platform-information/support-policy-java/
10. Download java v17 from https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html
11. Jenkins is usually installed on servers and not on client machines
12. Jenkins tool is used by Developers, QA engineers as well as DevOps teams
13. Visit https://www.jenkins.io/ for more details about Jenkins
14. Download Jenkins from https://www.jenkins.io/download/
15. Download jenkins generic java war package (.war)

16. To start jenkins, run the below command from jenkins.war path on your laptop:

                               java -jar jenkins.war

17. In the logs, observe for the UN & PWD and make a note of it [default UN: admin]
18. Wait until you see this message ‘Jenkins is fully up & running’

19. You can find your jenkins password at this location as well: C:\Users\Kiran\.jenkins\secrets\initialAdminPassword
    
    
    

20. To launch jenkins on your browser, visit http://localhost:8080
21. Complete the jenkins setup process by entering admin password

22. In the next page, click on ‘Install suggested plugins’ and wait until the plugins installation is completed

23. In the next screen, Jenkins will prompt you to create another user account. We can click on Skip and continue as admin

24. In the next screen, you will see Jenkins configuration details i.e., URL to launch Jenkins tool. Click on Save and Finish

25. In the next screen, click on Start using Jenkins

26. Now, the user will be taken to the home page of Jenkins where we can create Jenkins job/project to work on Continuous Testing process

27. Click on New item → enter the project name → click on Free style project → click on OK → Enter the description (optional) → under ‘Source code management’, select ‘None’ option → enter the cron job as * * * * * → this cron job will run our accessibility test for every 1 minute → see below screenshot
    

28. Use the below build triggers to run the jenkins project automatically

@hourly → this will run jenkins project every 1 hour

@daily → this will run jenkins project once in a day

@weekly → this will run jenkins project once in a week

@monthly → this will run jenkins project once in a month

@yearly → this will run jenkins project once in a year

* * * * * → this will run jenkins project every 1 minute

29. Under Build Environment, select ‘Add timestamps to the Console Output’
    
    

30. Under build steps, select ‘Execute Windows batch command’ → enter the required command based on the tool used for accessibility testing (eg. see below screenshot)→ click on apply → click on save

31. Observe that Jenkins will run the job/project as per configured Build Triggers
32. Observe the ‘Build history’ → Click on the Build number → Click on Console Output to view the console logs of the automation code test execution

33. To trigger emails from Jenkins, configure SMTP email server details in Manage Jenkins → System → Email notification as shown below → The below SMTP details are needed to configure : SMTP server name, User Name, Password, SMTP port number
34. Click on ‘Test configuration by sending test email’ to check if the configuration done is working or not

35. Configure Post-build actions in Jenkins job → Email notification