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

UI fails to set ECS Task Creation Timeout

    XMLWordPrintable

Details

    Description

      Attempting to set the ECS task timeout through the Jenkins web interface fails.

       

      This appears to be due to the typo correction for slaveTimoutInSeconds not being performed in https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/plugins/amazonecs/ECSCloud/config.jelly 

       

      As a result, it's still trying to set slaveTimoutInSeconds instead of slaveTimeoutInSeconds. Similarly, it doesn't display the current value due to the same issue.

       

      This is using version 1.19 of the plugin.

      Attachments

        Activity

          michaelward Michael Ward created issue -
          michaelward Michael Ward made changes -
          Field Original Value New Value
          Description Attempting to set the ECS task timeout through the Jenkins web interface fails.

           

          This appears to be due to the typo correction for slaveTimoutInSeconds not being performed in [https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/plugins/amazonecs/ECSCloud/config.jelly

           

          As a result, it's still trying to set slaveTimoutInSeconds instead of slaveTimeoutInSeconds. Similarly, it doesn't display the current value due to the same issue.
          Attempting to set the ECS task timeout through the Jenkins web interface fails.

           

          This appears to be due to the typo correction for slaveTimoutInSeconds not being performed in [https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/plugins/amazonecs/ECSCloud/config.jelly

           

          As a result, it's still trying to set slaveTimoutInSeconds instead of slaveTimeoutInSeconds. Similarly, it doesn't display the current value due to the same issue.

           

          This is using version 1.19 of the plugin.

          this seems to be fixed in the current state of the github repo (altough not released)

          webrat Andreas Sieferlinger added a comment - this seems to be fixed in the current state of the github repo (altough not released)

          People

            roehrijn2 Jan Roehrich
            michaelward Michael Ward
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: