Before actual applying the implemented DevOps solution for automated delivering of your project to production, it is recommended to find out whether it works as intended during all of the flow stages. For that, all the specified Jenkins jobs should be manually consecutively called so you can check the interaction of different delivery phases and reveal the possible errors or misconfigurations.
So, let’s see how each of our added Jenkins jobs acts. For that, we’ll run them one by one according to the mentioned flow:
Create Environment > Build and Deploy > Dev Tests > Migrate to QA > QA Tests > Migrate to Production
To execute a particular item, click on the triangle icon next to it and select the Build Now option within the shown context menu:
The progress of processing each job can be tracked either through the Jenkins output (Console Output option at a particular build’s context menu) or by using the appropriate log files within your Jenkins container.And below you’ll find the list of expected results upon running our scripts by means of these jobs: