An Azure DevOps Extension for deploying to Vercel from Azure Pipelines
by vercelLast 12 weeks · 0 commits
3 of 6 standards met
Problem When using to deploy a project in a subdirector the vercel pull command runs without the argument, while vercel deploy correctly includes it. This causes vercel pull to create the .folder in the repository root, but looks for it in the subdirectory. Since the isn't found, Vercel cannot detect the framework configuration. This results in "No framework detected" in deployment logs and Only static assets being deployed instead of the full application (serverless functions, SSR pages, etc.) Fix Add the --cwd argument to vercelPullArgs when vercelCurrentWorkingDirectory. Testing I _have not_ tested this (apologies), but we've included this in our workaround in a pipeline.
Version 2 introduced an issue with the Vercel CLI, which seems to still use the implicitly. By changing the envs name to this was broken, can be seen in this run: https://dev.azure.com/philippdollst/azdo-vercel-microfrontend-previews/_build/results?buildId=39&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=c40fb2b7-52be-5f30-27ae-93b0ff067608&l=27 When the is provided the run will succeed with v3 and the Node deprecation warnings disappear as expected: https://dev.azure.com/philippdollst/azdo-vercel-microfrontend-previews/_build/results?buildId=37&view=results Difference between first and second run in the pipeline: https://dev.azure.com/philippdollst/azdo-vercel-microfrontend-previews/_git/microfrontends-preview/commit/3d66eeaf615e15a3c771be2c027323bf58cc9e1b?refName=refs%2Fheads%2Fplugin-v3 The change in this PR should be the least invasive workaround to fix this for now @paulogdm Sorry for the delayed feedback - was kinda busy lately... would appreciate if you could take look into this soonish to unblock v3 and everyone cat get away from the Node 16 deprecation! I'll rerun the pipeline as soon as there's preview and in theory it should just work
Repository: vercel/vercel-azure-devops-extension. Description: An Azure DevOps Extension for deploying to Vercel from Azure Pipelines Stars: 35, Forks: 12. Primary language: TypeScript. Languages: TypeScript (89%), JavaScript (11%). License: MIT. Topics: azure-devops, azure-pipelines, vercel. Open PRs: 2, open issues: 4. Last activity: 3mo ago. Community health: 62%. Top contributors: phidol, codybrouwers, pawlean, EndangeredMassa, aldosch, healeycodes, Ethan-Arrowood, fruitymedley, MFCo, merckxite and others.
TypeScript
Hi all, I'm troubleshooting why my environment variables specified in the are not picked up by the application. Using this pipeline code In the logs, I see (Vercel CLI 41.1.1): . When I check further debug logs I can't see these variables in the"Deployment response": When I run via cli (Vercel CLI 41.1.0) from my shell the environment configuration is picked up by the application. Also, I can see these KEY1 and KEY2 variables in the further output of "Deployment response": Any thoughts? UPDATE: Wrote manually in the pipeline: vercel link + vercel deploy with the same arguments, and it worked.