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

Remove idle executors causes index out of bounds when docker plugin creates a new cloud

      The removal of idle executors in Jenkins weekly releases (PR-9177) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

      Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
      java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
      

      The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

      Steps to duplicate the issue in a clean environment:

      1. Create a plugins.txt with the list of plugins to be installed
      2. Create a run-jenkins.sh script that downloads Jenkins 2.470 and the defined plugins
      3. Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
      4. Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
      5. Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
      6. Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from "Manage Jenkins" -> "System log"

          [JENKINS-73554] Remove idle executors causes index out of bounds when docker plugin creates a new cloud

          Mark Waite created issue -
          Mark Waite made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Mark Waite made changes -
          Attachment New: run-jenkins.sh [ 63102 ]
          Attachment New: plugins.txt [ 63103 ]
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a plugins.txt file with the list of plugins to be installed
          # Create a run-jenkins.sh script that downloads Jenkins 2.470 and the defined plugins
          # Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a run-jenkins.sh script that downloads Jenkins 2.470 and the defined plugins
          # Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a run-jenkins.sh script that downloads Jenkins 2.470 and the defined plugins
          # Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the run-jenkins.sh script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases ([PR-9177|https://github.com/jenkinsci/jenkins/pull/9177]) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          Mark Waite made changes -
          Remote Link New: This issue links to "PR-9177 - Core pull request that removed idle executors, seems to cause the exception (Web Link)" [ 29900 ]
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases ([PR-9177|https://github.com/jenkinsci/jenkins/pull/9177]) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to try to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases ([PR-9177|https://github.com/jenkinsci/jenkins/pull/9177]) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          Mark Waite made changes -
          Description Original: The removal of idle executors in Jenkins weekly releases ([PR-9177|https://github.com/jenkinsci/jenkins/pull/9177]) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from
          New: The removal of idle executors in Jenkins weekly releases ([PR-9177|https://github.com/jenkinsci/jenkins/pull/9177]) causes a Jelly expression exception message when attempting to modify a newly created Docker cloud after using the docker plugin to create a new cloud of type "Docker". The exception message is:

          {code}
          Caught exception evaluating: !builtInHasExecutors and computers.get(0).node == app and computers.size()
          java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
          {code}

          The issue is only visible with Jenkins weekly releases 2.463 and later. It is not visible with the most recent Jenkins 2.452.3 LTS or with the Jenkins 2.462.1 release candidate.

          Steps to duplicate the issue in a clean environment:

          # Create a [^plugins.txt] with the list of plugins to be installed
          # Create a [^run-jenkins.sh] script that downloads Jenkins 2.470 and the defined plugins
          # Run the [^run-jenkins.sh] script and complete the setup wizard by installing no additional plugins and creating a new user
          # Configure 0 executors on the controller with "Manage Jenkins" -> "System" (this is a critical step, if this step is not performed, the error does not appear)
          # Define and save a new cloud using "Manage Jenkins" => "Cloud" and choosing type "Docker"
          # Open the configuration page of the newly created cloud and see the exception in the console output and in the Jenkins log from "Manage Jenkins" -> "System log"

            mawinter69 Markus Winter
            markewaite Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: