Skip to content

[integ-tests] Test the published artifacts in the release process tests - #7719

Merged
hanwen-cluster merged 1 commit into
aws:developfrom
hanwen-cluster:release-process
Nov 20, 2026
Merged

hanwen-cluster merged 1 commit into
aws:developfrom
hanwen-cluster:release-process

Conversation

@hanwen-cluster

Copy link
Copy Markdown
Contributor

Description of changes

In short, this commit increases coverage release-process.yaml while reduing the overall runtime.

The release flow runs these tests after the AMIs and the S3/ECR artifacts are published, and before the CLI is pushed to PyPI. test_essential_features re-verified features already covered on the same AMIs by develop.yaml, and it was the longest test of the run (79-102 min).

Replace it with tests that use the published artifacts:

  • test_slurm_cli_commands: the CLI about to be released, on a public AMI.
  • test_cluster_create (custom resource): the released Lambda layer.
  • test_build_image_custom_components: the released cookbook and Cinc installer, with the public AMI as parent image.
  • test_api_infrastructure_with_default_parameters (kept): the released API template, OpenAPI spec, policies, Lambda layer and ECR image.

Tests

release-process.yaml has passed in China, commercial, GovCloud

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

In short, this commit increases coverage release-process.yaml while reduing the overall runtime.

The release flow runs these tests after the AMIs and the S3/ECR artifacts are
published, and before the CLI is pushed to PyPI. test_essential_features
re-verified features already covered on the same AMIs by develop.yaml, and it
was the longest test of the run (79-102 min).

Replace it with tests that use the published artifacts:
- test_slurm_cli_commands: the CLI about to be released, on a public AMI.
- test_cluster_create (custom resource): the released Lambda layer.
- test_build_image_custom_components: the released cookbook and Cinc
  installer, with the public AMI as parent image.
- test_api_infrastructure_with_default_parameters (kept): the released API
  template, OpenAPI spec, policies, Lambda layer and ECR image.
@hanwen-cluster
hanwen-cluster requested review from a team as code owners November 20, 2026 19:03
@hanwen-cluster hanwen-cluster added the skip-changelog-update Disables the check that enforces changelog updates in PRs label Nov 20, 2026
@hanwen-cluster
hanwen-cluster merged commit 8a495d9 into aws:develop Nov 20, 2026
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog-update Disables the check that enforces changelog updates in PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants