I noticed a race condition with the GitHub Webhooks -> Azure Functions automation we currently use to publish ingest.json into https://evergreen.jenkins.io

The Azure Function relies on built information coming out of ci.jenkins.io, this ensures that we actually have passing tests and valid build artifacts, before it takes that information and publishes it to evergreen.jenkins.io

The Function relies on lastSuccessfulBuild, which at the time when the GitHub Webhook fires (on a merge), will always be commit-1

1. 1. Potential solution

The Pipeline could potentially also ping the Azure Function with information upon completing a master branch Run.