Add flag to skip build-distrubution execution step when release #2397
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 pull request do?
In order to fix this issue, a flag has been added to skip build-distribution execution step when the workflow is being executed from a release tag.
Also a dependency between the main build-distribution step in the
release.yml
and the invocation to thetest-release.yml
has been added to ensure the right order in case of uploaded artifacts should be used somewhere.This change is because two build-distribution steps trying to upload the same artifact are being executed in the same workflow: in the
release.yml
and in thetest.yml
. It basically is causing the conflict error here:Related issues
https://github.com/elastic/observability-robots/issues/2978