adding IsLatestReleaseUsingBuildDefinitionArtifact #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…se definition for the build's latest releaseand if its latest release contains any artifact regarding the build itself. This is in case the Build Definition has changed (ej. reused to target a monorepo) so even the repo is deprecated, the release is not and should not be deleted. This is returned in a property inside the pipeline, in the ToPipeline, it will now contain the Properties collection containing the Property "IsReleaseUsingBuildArtifacts" as "True" or "False" (string).
|
As mentioned tried to test it locally but did not fully work, so maybe I am not building/deploying properly in local... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adding IsLatestReleaseUsingBuildDefinitionArtifact to check the release definition for the build's latest releaseand if its latest release contains any artifact regarding the build itself. This is in case the Build Definition has changed (ej. reused to target a monorepo) so even the repo is deprecated, the release is not and should not be deleted.
This is returned in a property inside the pipeline, in the ToPipeline, it will now contain the Properties collection containing the Property "IsReleaseUsingBuildArtifacts" as "True" or "False" (string).
Addresses
That the release definition might have changed (reused) while still having a relation to the Repositoy/Build Pipeline (we might have executed releases with old artifact definitions, when they are not used anymore).
In this case, it is convenient to check this and highlight it in the UI so that the Release is not archived-deleted.