Skip to content

Conversation

@musa-asad
Copy link
Contributor

@musa-asad musa-asad commented Nov 5, 2025

Description of the issue

There is no mechanism to run the EKS E2E tests prior to a release and the weekly cron job isn't monitored. This overlooks common start-up issues that could occur for the Amazon CloudWatch Observability EKS add-on when providing a configuration using helm.

Description of changes

  • Add StartEKSE2ETests to build-test-artifacts.yml, which triggers e2e-test.yml.
  • Modified e2e-test.yml to accept build_run_id and build_sha, include CheckBuildTestArtifacts, and skip BuildAgent if build_run_id and build_sha is provided.

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests

Workflow Status
View Workflow Run #19091066216

Requirements

Before commiting your code, please do the following steps.

  1. Run make fmt and make fmt-sh
  2. Run make lint

Integration Tests

To run integration tests against this PR, add the ready for testing label.

@musa-asad musa-asad self-assigned this Nov 5, 2025
@musa-asad musa-asad added the ready for testing Indicates this PR is ready for integration tests to run label Nov 5, 2025
@musa-asad musa-asad marked this pull request as ready for review November 5, 2025 04:12
@musa-asad musa-asad requested a review from a team as a code owner November 5, 2025 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for testing Indicates this PR is ready for integration tests to run

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant