Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 21, 2025

What does this PR do?

Removes upload of build/** from integration tests steps since that would cause uploading everything (including subdirectories) under build/ including reuploading large elastic-agent packages (already uploaded at the packaging steps)

It also introduces more "precise" artifacts download from the packaging steps leveraging platform and package formats.

Why is it important?

To reduce wasted space and time in CI builds

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?
  • ...

This is an automatic backport of pull request #11327 done by [Mergify](https://mergify.com).

* avoid uploading the whole build/ directory tree

* Download only required artifacts for integration tests

(cherry picked from commit 3cedabf)

# Conflicts:
#	.buildkite/bk.integration.pipeline.yml
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Nov 21, 2025
@mergify mergify bot requested review from a team as code owners November 21, 2025 15:22
@mergify mergify bot requested review from blakerouse and michel-laterman and removed request for a team November 21, 2025 15:22
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Nov 21, 2025
@mergify mergify bot assigned pchila Nov 21, 2025
@mergify mergify bot added the backport label Nov 21, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Nov 21, 2025

Cherry-pick of 3cedabf has failed:

On branch mergify/bp/9.1/pr-11327
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit 3cedabfc0.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/bk.integration.pipeline.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@pchila pchila enabled auto-merge (squash) November 21, 2025 15:26
@pchila pchila merged commit d63a2ff into 9.1 Nov 21, 2025
20 of 21 checks passed
@pchila pchila deleted the mergify/bp/9.1/pr-11327 branch November 21, 2025 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport ci conflicts There is a conflict in the backported pull request 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