-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Docker Jenkins LTS 2.138.2 with Amazon ECS Plugin 1.17
The ECS cloud is configured to use a Task Definition ARN and not to create the task definition for us
-
-
v1.18
After upgrading the Amazon ECS plugin from 1.16 to 1.17 all ECS slaves fail to start with the exception below:
Nov 02, 2018 1:55:28 PM hudson.slaves.NodeProvisioner$2 run
WARNING: Unexpected exception encountered while provisioning agent ECS Slave ecs-agent
java.lang.NullPointerException
at com.cloudbees.jenkins.plugins.amazonecs.ECSService.runEcsTask(ECSService.java:303)
at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)
at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:227)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Which points to this line: https://github.com/jenkinsci/amazon-ecs-plugin/blob/amazon-ecs-1.17/src/main/java/com/cloudbees/jenkins/plugins/amazonecs/ECSService.java#L303
Looking at the code and the changelog I suspect that the changes introduced to allow VPC networking support work on the assumption that the task definition template is available but that is not true for us as we pass a pre-configured Task Definition ARN to the cloud configuration.
