Relying on the release manager for our ES snapshots has had some issues we are looking to resolve.

• A breaking change being merged into Elasticsearch causes CI to be in a failed state
• It can be really long between successful release manager builds (1 month+)
• When bumping versions, we must pin the snapshot to a previous artifact until the release manager produces a successful subsequent build.

To accomplish this, we should create a nightly job that will build Elasticsearch and run Kibana tests against it. If the tests are successful, we will promote the ES snapshot to Google Cloud bucket. If they are unsuccessful, we need to be notified either by an issue being created or a Slack notification to the operations channel.