Mercurial pushlog vs CI/CD logs: correlating pushes with deployment failures

Goal

Determine which Mercurial push triggered a CI‑build that subsequently failed to deploy.

Constraints

• The pushlog extension records only push metadata (user, time, list of nodes). It does not include build status.
• Changesets can be in draft or secret phases, meaning they may not appear in the standard hg log view that the CI system consumes.
• Enabling verbose pushlog or debug logging can increase server I/O and affect performance on busy repositories.

Unresolved Decision

How to reliably map a CI failure to a specific changeset when phase visibility and logging verbosity are uncertain.

Questions

1. Which pushlog fields (e.g., push_id, user, push_timestamp) can be used to uniquely identify the changeset that caused a deployment failure?
2. What strategy should be employed to handle secret or draft changesets that are not present in the CI’s hg log output?
3. How can pushlog verbosity be tuned to provide sufficient diagnostic detail without degrading repository performance?