[BuildKite] Make Failed Builds Visible Again

[nicpenning]

Since the move to Build Kite, community developers no longer have access to see why their builds fail when an Elastic member runs /test.

It would be very helpful if the developer of the integration can see what error messages have spawned so that they can be fixed instead of waiting on a response from an Elastic member to share the error details. This will decrease time to release if error messages on build can be revealed. The other solution is ensure all tests can be executed locally using elastic-package: elastic/elastic-package#1721

[efd6]

This should be fixed. Please take a look at a recent build to confirm.

[nicpenning]

This has been resolved! I can see build information now, thank you! 🙏

[jsoriano]

Reopening, we had to revert the changes because we had problems triggering internal pipelines from the public pipeline. We will split the pipeline in two, a public one with the main validation stages, and a private one with the stages that trigger internal processes.

cc @mrodm

[nicpenning]

Thanks for the awareness, @jsoriano !

[mrodm]

We will split the pipeline in two, a public one with the main validation stages, and a private one with the stages that trigger internal processes.

Following about this, there are some steps that need to be done in order to make public the pipeline in charge of testing/validating packages:

• Move publishing steps to a new pipeline (in dry run mode) Add Buildkite pipeline to publish packages (DRY_RUN mode enabled) #9553
• Update permissions for this new pipeline
• Enable publish step in that new pipeline and test to publish some package in main branch
• Copy these changes to all backport branches
• Update catalog-info settings to run this pipeline also for backport branches
• Set testing pipeline as public

[mrodm]

All the changes to make the pipeline again public have been completed, and now the pipeline should be public again. Please, take a look at a recent build to confirm @nicpenning.

[nicpenning]

Looks great!

[mrodm]

Perfect! Thanks for checking this out @nicpenning!
I'll close this issue then.

[nicpenning]

This is great, thank you for this implementation. It will help greatly for those in the community developing integrations.