Skip to content

Buildkite: install libyaml-perl when missing on PR agents - #3353

Merged
reakaleek merged 1 commit into
masterfrom
fix/install-libyaml-perl-on-agent
Aug 7, 2026
Merged

Buildkite: install libyaml-perl when missing on PR agents#3353
reakaleek merged 1 commit into
masterfrom
fix/install-libyaml-perl-on-agent

Conversation

@reakaleek

Copy link
Copy Markdown
Member

Why

  • legacy_branches.pl needs Perl YAML.pm on the host agent, but some docs-ubuntu images do not have libyaml-perl
  • When the module is missing, the skip guard fails open and the pipeline clones and builds anyway (for example full Kibana PR builds)

What

  • Install libyaml-perl at the start of the legacy-branch check when YAML.pm is not already available

Notes

  • This is a pipeline-side guard while the agent image is updated
  • main/master still exit early before this install path

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@reakaleek
reakaleek requested a review from a team as a code owner August 7, 2026 12:20
@reakaleek
reakaleek requested a review from Mpdreamz August 7, 2026 12:20
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@reakaleek
reakaleek enabled auto-merge (squash) August 7, 2026 12:21
@reakaleek
reakaleek merged commit 656f93e into master Aug 7, 2026
4 of 5 checks passed
@reakaleek
reakaleek deleted the fix/install-libyaml-perl-on-agent branch August 7, 2026 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants