I found it. When setting up the Spot fleet on the AWS console, the
"Maintain target capacity" must be checked.
On Monday, January 18, 2021 at 2:33:07 PM UTC-5 zil...@gmail.com wrote:
> Jenkins v2.263.1
>
> In the AWS Spot Fleet console, I set up a spot fleet from a launch
> template, with 10
Hi, I deploy jenkins via jenkins/jenkins helm to kubernetes. I was hoping
to use the "Kubernetes Credentials Provider" plugin to store
ssh-credentials but this does not really seem to work when running a groovy
pipe from scm and running on kubernetes agents. It seems the credential is
not
Jenkins v2.263.1
In the AWS Spot Fleet console, I set up a spot fleet from a launch
template, with 10 on-demand instances, in the SAME region, AZ, VPC, and SG
as my Jenkins master node, and it wen't to the "Fulfilled" state.
Now when I go to Manage Jenkins -> Manage Nodes and Clouds ->
It turns out my builder block was set up with the wrong security group.
Once I set this up correctly, the above configuration worked.
On Wednesday, January 13, 2021 at 4:06:35 PM UTC-5 zil...@gmail.com wrote:
> I'm trying to create an AMI (for Jenkins master in this case), and I have
> the
