1124417 - move run_build_repos_sync.sh off github-sync2.dmz.scl3

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Hal Wine [:hwine] use NI!]

Need to find a new home for this job.

Obvious candidates include:
 - interim move onto github-sync3
 - AWS

Comment 1

[Hal Wine [:hwine] use NI!]

Looks like 4GB disk needed:

[[e-mail]3 ~]$ du -csh *
24K	bin
3.6G	initial3.tar.bz2
1.3G	mozilla-cvs-history.tar.bz2
3.5G	vcs_sync
8.2G	total

ni :pete - how much headroom do we need above the 3.5G currently used "at rest"?

Comment 2

[Pete Moore [:pmoore][:pete]]

Looks like if we fail a staging clone, we blow it away before recloning, rather than parking:
http://hg.mozilla.org/build/mozharness/file/af1461521190/scripts/vcs-sync/vcs_sync.py#l353

Growth of our repositories as new commits / repos are added over time, and potential refactorings or new functionality will draw more demands on disk space.

Therefore I would say lets make sure we have an absolute minimum of a further 3.5GB headroom to allow our repos to double in size over time. 10-20GB headroom would be better if possible, e.g. often useful when troubleshooting, making temporary backups for later inspection during a recovery operation, or future refactorings/features. Currently we have 53GB free on github-sync2.

Comment 3

[Hal Wine [:hwine] use NI!]

This is now running from dev-services aws instance.