Change Details

Harbormaster build logs are mostly okay up to the storage part and then garbage from there forward. In particular: - (T5822) They should support archiving and GC. - (T9124) They should be accessible via the API -- but note issues with T5955 for logs with ANSI character codes. - (T9516, T8656, PHI382, T10179) The UI is generally clumsy and managing large logs is a headache. - (T6139) Build logs should support summarization. - (T11810) Live log output. - (T10868) Line-anchors.

Harbormaster build logs are mostly okay up to the storage part and then garbage from there forward. In particular: - (T5822) They should support archiving and GC. - (T9124) They should be accessible via the API -- but note issues with T5955 for logs with ANSI character codes. - (T9516, T8656, PHI382, T10179) The UI is generally clumsy and managing large logs is a headache. - (T6139) Build logs should support summarization. - (T11810) Live log output. - (T10868) Line-anchors. The source code CSS changes have made `{P123}` render a little weirdly, and it should get a pass before this finishes up.

Harbormaster build logs are mostly okay up to the storage part and then garbage from there forward. In particular: - (T5822) They should support archiving and GC. - (T9124) They should be accessible via the API -- but note issues with T5955 for logs with ANSI character codes. - (T9516, T8656, PHI382, T10179) The UI is generally clumsy and managing large logs is a headache. - (T6139) Build logs should support summarization. - (T11810) Live log output. - (T10868) Line-anchors. The source code CSS changes have made `{P123}` render a little weirdly, and it should get a pass before this finishes up.