407680 - staging release automation should clean externalStagingServer

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Robert Helmer [:rhelmer]]

The current release automation scheme uses a central "console" server where the release is prepared and staged, which is referred to in the config as stagingServer. The public areas are synced periodically to externalStagingServer.

For the staging release automation systems, we should add a buildbot step after "create staging area" that re-syncs stagingServer/externalStagingServer and removes any out-of-date files (e.g. "rsync --delete stagingServer:/home/ftp externalStagingServer:/home/ftp").

This step is only applicable to staging, as the purpose is to provide access to past releases for verification purposes (which will always be there in production), and to keep the staging machines from running out of disk space.

Comment 1

[Robert Helmer [:rhelmer]]

Attachment: [checked in] clean external staging area

Comment 2

[Robert Helmer [:rhelmer]]

Comment on attachment 292557 [details] [diff] [review]
[checked in] clean external staging area

Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/staging/master.cfg,v  <--  master.cfg
new revision: 1.9; previous revision: 1.8
done