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

System groovy script file succeeds on build slave when script does not exist

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • groovy-plugin
    • None

      Configure a job to run on a non-master node, and define an "Execute system Groovy script" that calls a "Groovy script file" called "test.groovy"
      "test.groovy" contains

      println("testing")

      If the file "test.groovy" doesn't exist in the non-master node's workspace the build step succeeds.

          [JENKINS-15516] System groovy script file succeeds on build slave when script does not exist

          jlpinardon added a comment -

          Additionnally, there is no alert on log console, which is a really a mess to understand why ... nothing occurs.

          jlpinardon added a comment - Additionnally, there is no alert on log console, which is a really a mess to understand why ... nothing occurs.

          arash m added a comment -

          In my testing I've noticed that the script in the "Groovy script file" box is completely ignored. When I enter a script path (an absolute path to the script on the Jenkins master host), there is no output in the log from any run or any attempt at a run.

          The behavior is the same as if I chose "Groovy command" and left the box blank.

          arash m added a comment - In my testing I've noticed that the script in the "Groovy script file" box is completely ignored. When I enter a script path (an absolute path to the script on the Jenkins master host), there is no output in the log from any run or any attempt at a run. The behavior is the same as if I chose "Groovy command" and left the box blank.

            vjuranek vjuranek
            namtabmai _
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: