Dynamically populate legal Detect Version options #67
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi maintainers! I am not sure exactly how to test this capability at this point, but if you can point me in the right direction I would be happy to test it myself, or you can assist me in testing before accepting the PR.
The basic idea is to fetch the potential legal detect versions from https://sig-repo.synopsys.com/artifactory/api/storage/bds-integrations-release/com/synopsys/integration/synopsys-detect/ and use those versions to populate the Detect Version pick list for the ADO task. We encountered a case of user error where the customer entered an invalid value here, so this would prevent such occurrences in the future.