Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12455

Deploy of ChromeDriver fails if destination folder doesn't exists

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • chromedriver-plugin
    • None
    • Linux (ubuntu), jenkins latest version (1.448)

      I have installed the the ChromeDriver plugin and "Multi slave config plugin" and created a few slaves with it. Once it tries to launch the slave, it creates the initial folder on the distant machine correctly frmo the multi slave plugin. The problem comes when it triggers the listener to install the ChromeDriver plugin, the tools folder doesn't exist in that work folder. The plugin then fails to install the ChromeDriver and the slaves dies.

      this should be fixed with a check if it exists, if not create the tools folder.

            Unassigned Unassigned
            darkrift Richard Lavoie
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: