Background: Back in 2019, I worked on a testing project where application development and maintenance were being done by one organization, and my organization did the testing. We usually start our day at 1 pm, and we expect the testing environments to be released with all hot fixes between 12 pm - 1 pm. There is no connected Jenkins pipeline between the organizations as both have their own on-premise Jenkins setup. This may look fine, but it is a typical problem with many service-based organizations. The problem here is we are losing 1 hour of time between the environment release and our day start. To save an hour, we planned to create an app that triggers the Jenkins pipeline from mobile to run pipelines whenever and from wherever we need it.
Goals: To trigger on-premise Jenkins pipelines from a mobile app.
Solution & Results: We approached the solution in four phases:
Jenkins made a difference by easing testers' lives with jobs, schedulers and pipelines. It decreased the dependency of knowledge for new joiners in the testing team to run sanity or any automation test cases/scripts.
For results we saw the following: