If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Sheriffs/community members should have access to all RelEng log files

NEW
Unassigned

Status

Release Engineering
General
3 years ago
5 months ago

People

(Reporter: pmoore, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Sheriffs should have access to all log files that RelEng generates.

For example:
foopy log files (from watch_devices.sh)
buildbot log files
runner log files
aws manager log files
bumperbot log files
vcs sync log files
mapper log files
relengapi log files

Some of these are per slave (e.g. build log files, runner log files) - and could be nicely integrated into slave health.

Others are individual services (aws manager, bumperbot) which only run on one machine and exist in one place.

Services written in mozharness already provide the ability to upload log files.

Publishing the log file(s) is not enough - we also need to link to, or display log files in our web interfaces, to make the job of access log files simpler.

This will also help releng too - not only sheriffs, e.g. if we can see log files directly from our own web interfaces.
(Assignee)

Updated

5 months ago
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.