Before I had used Jenkins, never felt the need for it.<\/p>\n
In reality, I \u2018Didn\u2019t know that I DIDN\u2019T KNOW!\u2019 (Stages of knowledge)..<\/p>\n
For a long time, I never felt the need for it, nightly runs would work fine, and life was merry<\/p>\n
The \u2018itch\u2019 began when other team members were not able to access the reports easily<\/p>\n
The common solution to this is sending a \u2018heap\u2019 of emails for which then the receivers have to use \u2018rules\u2019 to pile them in specific folders straight away<\/p>\n
All I wanted was a central place from where everyone can access the results<\/p>\n
As time passed and we became proficient with Jenkins, now I feel we cannot survive without it!<\/p>\n
When I think back to the \u2018simpler\u2019 days, there was A LOT we were not able to do and facilitate consuming automation\u2019s results<\/p>\n
Bottom line, if you are not using some form of CI tool like Jenkins, do consider it even if there is no plan for CI \/ CD in your team.<\/p>\n
#QsDaily #automation #continuousintegration #jenkins<\/p>\n<\/div>