Closed jnewton03 closed 4 years ago
I tried again today by changing to a different fleet and continue to get messages like the below even though my fleet has capacity of 1. It seems changes to the configuration do not take effect without a Jenkins reboot:
currentDemand -1 availableCapacity 2 (availableExecutors 0 connectingExecutors 0 plannedCapacitySnapshot 2 additionalPlannedCapacity 0)
I tried again today by changing to a different fleet and continue to get messages like the below even though my fleet has capacity of 1. It seems changes to the configuration do not take effect without a Jenkins reboot:
currentDemand -1 availableCapacity 2 (availableExecutors 0 connectingExecutors 0 plannedCapacitySnapshot 2 additionalPlannedCapacity 0)
@jnewton03 Can you verify this still occurs after installing the 1.16.2 release?
@DerkSchooltink I will upgrade and if there are still issues I'll post them here. Thanks for the heads up! :)
I have been doing some testing with this plugin to replace the EC2 plugin. I created several different fleets and have been testing with a number of builds. However, when I try to start additional builds, the fleet never scales up. Here is what I see in the logs:
However, when I show my fleet, it is never scaling up: Total target capacity 1 (1 fulfilled)
On-Demand capacity 0 (0 fulfilled)