Ensure ddev release tag fetches tags before getting the full list #20292
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 PR do?
This PR modifies the current behavior of the
ddev release tag
by first fetching the list of tags. This is to ensure that when the full list of tag is going to be compared against current versions we have the most up to date version in origin.In order for this to work in
integrations-core-pipeline
we need to update the tagger image afterdatadog-checks-dev
newer version has been released with an updated dependency inddev
with this package. While this is not done (comming in a future PR) this change won't have any effect in the pipeline. The reason is that we are buildingddev
with thebuild
package which ignores the local linking done by hatch in environments locally.I also added an option to the gitlab file to manually trigger the tagger and image log integrations validations images. If we keep the
ddev
dependency as it is now, patch updates on thedatadog-checks-dev
package won't trigger a build since there is no change in the ddev dependency list.Motivation
Ensure all tags are available when running
ddev release tag
.Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged