feat: align GitLab and Azure setup features - #152
Draft
fengmk2 wants to merge 2 commits into
Draft
Conversation
Contributor
✅ GitLab E2E passedCommit: |
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.
GitLab and Azure now support version files, Node.js selection, project
.npmrcauthentication, and full YAML install inputs. The runtimes also retry the knownsfwcommand-lookup failure.GitLab adds a Windows template, native cache controls, and outputs in
.setup-vp-outputs.env. Azure adds named outputs and a cache forsfw.On Azure,
nodeVersionnow selects the project runtime throughvp env use.bootstrapNodeVersioncontrolsUseNode@1.Azure E2E tests remain out of scope.
Cache@2still has no supported restore-only control.