title: After chrome's auto update, selenium chromedrivers become redundant : Standard way to handle this in CI Environment
body: <p><strong>UseCase:</strong></p>
  
  <p>After the chrome browser gets updated, UI automated testing with selenium ( which uses a older chromedriver) is unable to run some of the automated test-suites.</p>
  
  <p>What is the standard automated way to cope-up with these updates ? </p>
  
  <p>stop auto-update of chrome browser in those CI ( continuous Integration ) machines 
  or 
  Is there any other standard automated way of doing this ?</p>