CP-7781 - switching bk pipeline to gpctl promote after synthetics

[mduarte]

Summary

Replacing pipeline gpctl-promote-with-e2e-tests with gpctl-promote-after-serverless-devenv-synthetics.
This will replace the execution of the E2E tests on promotion to dev/qa with the execution of the synthetics tests.

[jbudz]

Is this no longer available? It was previously helpful for us to run this pipeline without promoting artifacts in support of testing pipeline changes on our side.

[mduarte]

This functionality was also not available in the previous pipeline.

Out of curiosity, have you tried to call this recently with DRY_RUN=true?
We do have a separate pipeline that only does the testing and no promotion.

[jbudz]

I'm mostly not involved with the Kibana release pipeline, not sure how this was used.

@pheyos @delanni can you take a look?

[delanni]

We used this flag while testing the migrations to ensure we triggered the right downstream. I don't know if it's still in use, or would have future uses.

For more context, we added the Kibana triggers here: https://github.com/elastic/kibana/pull/178658/files

the corresponding escape hatch was added to promote.sh here: https://github.com/elastic/gpctl/pull/261

It's true, that the gpctl-promote-with-e2e-tests pipeline didn't have a reference to DRY_RUN, but I believe, it did work for our case using the gpctl-promote pipeline, as we directly triggered that (and thus the env section from the first linked PR was passed on). Through gpctl-promote-with-e2e-tests this is probably lost, unless we pass along the env to the trigger step.

I don't think we're using the DRY_RUN for any other use cases right now. So we can either add env passing there, or allow this to be removed for now. I'd go for the first option, since the hatch exists in promote.sh, we may as well expose it.

[mduarte]

I've added support for a more explicit env variable called GPCTL_PROMOTE_DRY_RUN in https://github.com/elastic/serverless-gitops/pull/4202.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: ff83b2e

Failed CI Steps

• FTR Configs #6

Test Failures

• [job] [logs] FTR Configs #6 / machine learning - anomaly detection anomaly explorer with influencers with farequote based multi metric job Anomaly Charts as embeddable attaches an embeddable to a case

Metrics [docs]

✅ unchanged

History

• 💔 Build #236971 failed c71d908
• 💛 Build #236163 was flaky 580ccab
• 💛 Build #235830 was flaky e413e5a
• 💔 Build #235689 failed 47ebb1b
• 💔 Build #235544 failed 6aad601b1b30b641535da425cc0a40bc8abe27ab

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream