[8.x](backport #5113) Ess terraform + run integration tests on BK agents #5736
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* ESS by terraforms * Use bk runners * added state to artifacts * Add common.sh to scripts * Add depends_on * Inlined paclage variables * tmp disbale unit tests * tmp disbale unit tests * install tf * install tf * install tf * install tf * fix ec creds * Added auto-approve * Test run * package again * package again * package again * package again * package * package * added mage build:testBinaries * Install mage * Install mage * Install mage * Install mage * Install mage * fix go * Merged * Merged * fix * fix * Fix tests * Debug * Use custom image * New suod tests * Test run * Test run * Test run * Debug * Debug * Debug * Debug * Debug * Cleanup * Using subshell in newgrp * Using subshell in newgrp * Test new custom VM image * Test new custom VM image * Set terraform version * Cleanup * terraform 1.9.3 * terraform 1.9.3 * Debug * Explicit image version * Explicit image version * Explicit image version * Sudo tests * +x * Try mage integration:local * Use gotestsum * Use gotestsum * Run sudo tests * Run sudo tests * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Increased test timeout * Groupped sudo tests * Quoted regexps * BK steps by groups * BK steps by groups * BK steps by groups * BK steps by groups * fix param propagation * Debug * Big run * reuse EC_API_KEY * Debug test * Debug a test * Revert debug * Debug * Html report * groupping, auto-retry, packaging * removed reruns * Reuse the initial ESS stack. Start a new stack for retries * Fix ess start path * Fix ess start path * Fix ess start path * Fix ess start path * Debug * Debug * Debug * Fix EC_KEY recovery * Added lock to artifacts * Fix artifacts download path * Fix artifacts download path * Fix artifacts download path * Removed unnecessaru build dependencies * Added build id * Separated BK integration tests to a dedicated pipeline * CLeanup * Applied proposed changes * Applied proposed changes * Applied proposed changes (cherry picked from commit 7aa8bb2)
mergify
bot
requested review from
blakerouse and
swiatekm
and removed request for
a team
|
swiatekm
approved these changes
Oct 9, 2024
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
A dedicated pipeline that runs Ubuntu integration tests directly on Buildkite runners without OGC. Currently it's not triggered by any of Github events.
Sudo tests build example
platform-ingest-elastic-agent-ubuntu-2204. All required packages are pre-installed and we don't need to install them in runtime;Shared ESS stack and test reruns
The
Start ESS stack for integration testsspins up an ESS stack that is used by following integration tests. When the tests are complete, the stack will be destroyed regardless of the test results. When we restart a single test group, it will start a dedicated stack and destroy it when the tests are complete.This type of pipeline is supposed to replace the existing single-step approach. Further upcoming changes a listed in the the meta-issue.
Why is it important?
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself
This is an automatic backport of pull request #5113 done by [Mergify](https://mergify.com).