autoscaler
autoscaler copied to clipboard
drone
Automatically adds or removes instances based on build volume
Change the default AWS AMI image for agents from 16.04 to 18.04 to avoid the deprecation notice.
Problem ======= Occasionally we've noticed that the autoscalers know about instances that the VM providers (e.g. GCP or AWS) don't or vice versa, probably due to latent bugs in the...
- Fix all regions have corresponding default AMI mapping. - Refresh outdated default images for AWS & GCP. - Change default instance type with latest `T3` series. - Support for...
Adds a driver implementing initial support for [Brightbox](https://www.brightbox.com) Cloud. The minimum required configuration is an API Client and Secret (https://www.brightbox.com/docs/reference/api-clients/) and a Server Group with a suitable Firewall Policy (https://www.brightbox.com/docs/reference/firewall/)...
Adds an option to set instance metadata service (IMDS) access option to require the usage of tokens (IMDSv2). The default value, "optional", will not change the current behavior.
Docker CE 20.10.7 https://marketplace.digitalocean.com/apps/docker We started getting some odd compilation errors in drone build, which appeared to be linked to the very old version of docker used by default in...
Adds the ability to specify the logging driver and options for the runner (agent), gc, and watchtower containers. Example config; ``` DRONE_AGENT_LOGGING_DRIVER=json-file DRONE_AGENT_LOGGING_OPTIONS=max-size:100m,max-file:5 ``` ref: https://docs.docker.com/config/containers/logging/configure/#supported-logging-drivers
Hi, I'm currently using this configuration: `DRONE_AGENT_CONCURRENCY=1`, `DRONE_CAPACITY_BUFFER=1`. When there is only 1 server, 1 running build, I expect the autoscaler to scale the num of servers to `2` but...
