• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MITLibraries / workflow / 35 / 4
78%
master: 75%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 11 Oct 2019 04:11PM UTC
Files 3
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Oct 2019 03:51PM UTC coverage: 78.431%. First build
TOX_ENV=coveralls

push

travis-ci-com

gravesm
Support worker autoscaling

Adding autoscaling to ECS for the worker service requires a few changes
to how the cluster is redeployed. Previously, everything was stopped by
setting the desiredCount to 0 and then started back up by setting the
desiredCount to 1. With ECS controlling the scaling for the worker
service it's no longer possible to rely on the desiredCount of the
worker service remaining at 0 until things are ready to be started
again.

The change here sets the desiredCount of the scheduler to 0 first, then
does a --force-new-deployment for the web and worker services, then
finally does a --force-new-deployment for the scheduler. While
redeploying becomes more complicated, there's no need anymore to track
the current worker count. We can just set it to 1 and let ECS scale as
needed.

I've also added stop-scheduler and start-scheduler commands which can be
used in conjunction with deploying a new service definition with
Terraform.

120 of 153 relevant lines covered (78.43%)

0.78 hits per line

Source Files on job 35.4 (TOX_ENV=coveralls)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 4
  • Travis Job 35.4
  • 9a65ce21 on github
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc