-
Bug
-
Resolution: Fixed
-
Minor
-
-
Evergreen - Milestone 2
-
ec2-plugin 1.40
When configuring an EC2 cloud using CasC, one must explicitly set userData to avoid getting an NPE during provisioning.
Here is the working yaml
--- jenkins: clouds: - amazonEC2: cloudName: "ec2" instanceCapStr: 20 zone: "us-east-1" useInstanceProfileForCredentials: true privateKey: "${PRIVATE_KEY}" templates: - description: "EC2 Agent" ami: "ami-0c6bb742864ffa3f3" labels: "agent" type: "T2Xlarge" remoteFS: "/home/ec2-user" remoteAdmin: "ec2-user" ################ # FIXME: without this, there's an NPE during provisioning userData: ""
Expected behaviour
If I do not need any userData, I should just be able to not specify it like above.
(the workaround being easy and obvious is the reason I put this as low priority).