Skip to content

[CI] Refactor script to run integration tests #2768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Jul 25, 2025
Merged

[CI] Refactor script to run integration tests #2768

Changes from 1 commit
Commits
Show all changes
15 commits
Select commit Hold shift + click to select a range
d8219a0
Move upload safe logs to a function
mrodm Jul 23, 2025
abe2903
Separate git clean target
mrodm Jul 23, 2025
dd84b2e
Remove if to check parallel or false positives targets
mrodm Jul 23, 2025
f13dc34
Add default value for UPLOAD_SAFE_LOGS
mrodm Jul 23, 2025
d214271
Define JOB_GCS_BUCKET_INTERNAL always
mrodm Jul 23, 2025
f6cfbb5
Add safeguard for uploading test logs
mrodm Jul 24, 2025
9aa9efb
Add another function to install tools
mrodm Jul 24, 2025
3a8ae6d
Fix function name to install kubernetes/kind
mrodm Jul 24, 2025
c1eed72
Merge upstream/main into refactor-integration-tests
mrodm Jul 24, 2025
c4dd938
Restore group title for uploading safe logs
mrodm Jul 24, 2025
34d59cc
Add target as part of the path to upload logs
mrodm Jul 24, 2025
0c32d2a
Remove common prefix from targets
mrodm Jul 24, 2025
a3af19f
Merge upstream/main into refactor-integration-tests
mrodm Jul 25, 2025
2fc8ba6
Add double quotes - fix lint warnings
mrodm Jul 25, 2025
d39eb61
Define variable as local in function
mrodm Jul 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Remove common prefix from targets
  • Loading branch information
@mrodm
mrodm committed Jul 24, 2025
commit 0c32d2af1ce2935b63bc2a9d26cda071f3abfdf6
7 changes: 6 additions & 1 deletion .buildkite/scripts/integration_tests.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,12 @@ upload_package_test_logs() {
echo "--- Uploading safe logs to GCP bucket ${JOB_GCS_BUCKET_INTERNAL}"

retry_count=${BUILDKITE_RETRY_COUNT:-"0"}
package_folder="${TARGET}.${PACKAGE}"
# Add target as part of the package folder name to allow to distinguish
# different test runs for the same package in different Makefile targets.
# Currently, just for test-check-packages-* targets, but could be extended
# to other targets in the future.
target=${TARGET#"test-check-packages-"}
package_folder="${target}.${PACKAGE}"
Comment on lines +82 to +83
Copy link
Contributor Author

@mrodm mrodm Jul 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added as part of the package folder the target that it is running.

If it is required to add with-logstash target to be run in parallel steps, there is a package that would be duplicated. system_benchmark is located twice in with-logstash and benchmarks folders.

That makes me think that if we create two packages with the same folder name in the the folders as:

  • test/packages/parallel/mypackage
  • test/packages/false_positives/mypackage

Logs from both executions would be uploaded to the same folder:
buildkite/elastic-package/PR-1234-456/insecure-logs/mypackage

Adding the target this would become:

  • buildkite/elastic-package/PR-1234-456/insecure-logs/parallel.mypackage
  • buildkite/elastic-package/PR-1234-456/insecure-logs/false-positivies.mypackage

Not added the full target name (test-check-packages-parallel or test-check-packages-false-positives) to be easier to find the files in the UI.


if [[ "${ELASTIC_PACKAGE_TEST_ENABLE_INDEPENDENT_AGENT:-""}" == "false" ]]; then
package_folder="${package_folder}-stack_agent"
Expand Down