Java Agent Main Build: Setting concurrency group #481
Merged
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.
Issue #, if available:
Description of changes:
The recent failures of this workflow (while merging series of dependabot PRs) looks like caused by multiple jobs of java-agent-main-build running at the same time: https://github.com/aws-observability/aws-otel-java-instrumentation/actions/runs/5550810364/jobs/10136412203#step:9:1450
We don't want the multiple EKS Operator tests to run on same cluster as same time, as Operator is installed on default namespace. To ensure this, adding concurrency group; and also setting
cancel-in-progress
job as false for this workflow.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.