Closed Bug 1455765 Opened 6 years ago Closed 6 years ago

buildbot slave share on AWS should be on EBS?

Categories

(Localization Infrastructure and Tools :: Administration / Setup, task)

Product:
Localization Infrastructure and Tools
Component:
Administration / Setup
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Pike, Unassigned)

References

Details

The first share of mozilla-central is really slow, like 15 minutes or so.

This is because the instance comes up from scratch, and needs a fresh checkout.

Should we add EBS storage to the buildbot instance (slave-side, if we split those), so that hg shares are kept between restarts?
The buildbot instance has EBS storage, however the volume is not persisted between instances. So, when the instance is _replaced_, there is a penalty on first clone. This will only happen on deploys; process restarts will incur no penalty.

I contend this will be infrequent enough in production to not cause too much harm.
Are we okay closing this?
Yeah.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.