Hi,

I'm using Jenkins 1.559 and Amazon EC2 of version 1.21

Once I start the build, instance with the desired label appears as pending 
for a moment, but after a few seconds it's replaces with shiny new instance 
created from AMI.
Also, if I set label in my task to match node label completely (i.e. it can 
only be started on the specified node), task will be pending until I 
manually launch the node on the Manage Nodes panel.

Could you confirm that resume feature works fine with On Demand instances 
as well?
Also, probably there is a problem with policy I set via IAM:

{
  "Statement": [
    {
      "Action": [
        "ec2:DescribeRegions",
        "ec2:DescribeInstances",
        "ec2:DescribeImages",
        "ec2:DescribeKeyPairs",
        "ec2:DescribeSubnets",
        "ec2:DescribeSecurityGroups",
        "ec2:DescribeAvailabilityZones",
        "ec2:CancelSpotInstanceRequests",
        "ec2:GetConsoleOutput",
        "ec2:RequestSpotInstances",
        "ec2:RunInstances",
        "ec2:StartInstances",
        "ec2:StopInstances",
        "ec2:TerminateInstances",
        "ec2:CreateTags",
        "ec2:DescribeTags"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}


понедельник, 28 апреля 2014 г., 6:01:37 UTC+7 пользователь jpd4nt написал:
>
> Hi Ilya.
>
> Can you provide which version of the plug-in you are using and what 
> version Jenkins you are using.
>
> I use the resume feature and its been working fine out of the box.
>
> It some times breaks but has not done that for a while.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to