This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 100
Remove the need for type of artifact and alias from Install/Checkout Tasks #151
Merged
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
azlam-abdulsalam
changed the title
Refactor/remove artifact type
Remove the need for type of artifact and alias from Install/Checkout Tasks
Sep 19, 2020
aly76
reviewed
Sep 21, 2020
let sfdx_package = tl.getInput("package", false); | ||
let skip_on_missing_artifact: boolean = tl.getBoolInput("skip_on_missing_artifact",false); | ||
|
||
let artifactDir = tl.getInput("aritfactDir",false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo on the artifact directory input
This was referenced Jan 29, 2022
This was referenced Jun 7, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This enhancement removes the need for asking the user for artifact type in Azure Pipelines. Classic Release pipelines and new YAML pipelines unpacks attached artifacts into a default artifact directory. This can be utilized to understand the artifact locations automatically by globing this directory.
Moreover, the enhancement also has an option for alternate artifact download directories, which could be anything the user is pointing to.