Skip to content

Conversation

@swiatekm
Copy link
Contributor

What does this PR do?

Why is it important?

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@swiatekm swiatekm added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team chore Tasks that just need to be done, they are neither bug, nor enhancements backport-active-all Automated backport with mergify to all the active branches labels Dec 10, 2025
@swiatekm swiatekm force-pushed the test/fix-docker-packaging-gocontainerregistry branch 3 times, most recently from fc83f28 to 1d395db Compare December 11, 2025 12:10
@swiatekm swiatekm force-pushed the test/fix-docker-packaging-gocontainerregistry branch from 1d395db to 767cb97 Compare December 11, 2025 19:43
@elasticmachine
Copy link
Contributor

elasticmachine commented Dec 11, 2025

💔 Build Failed

Failed CI Steps

History

cc @swiatekm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches chore Tasks that just need to be done, they are neither bug, nor enhancements skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants