I want to install Azure Site Extension from Azure DevOps feed, and not nuget.org
I cannot find any instruction, except this link (5 years ago):
https://azure.microsoft.com/en-gb/blog/writing-a-site-extension-for-azure-websites/
Didn't work for me. Just stack on this screen:
Any suggestions how to achieve this?
Update 1
I browsed to kudu, and saw this:
Which gave me an idea to remove all previously installed site extensions. After doing this, I was able to see packages uploaded to myGet. So, now the main question. How to do this for Azure DevOps feed?
Update 2
I tried to set SCM_SITEEXTENSIONS_FEED_URL to my private feed in azure devops, but I get following error on kudu:
Failed to retrieve site extensions from Gallery - An error has occurred. - Kudu.Contracts.SiteExtensions.InvalidEndpointException - Invalid remote feed url: https://****.pkgs.visualstudio.com/_packaging/****/nuget/v3/index.json
It looks like kudu cannot connect to feed. I tried to edit nuget.config on target website, and add packageSourceCredentials. didn't help. However, manual install with nuget cli from kudu powershell was successful.
So, now the main question. How to do this for Azure DevOps feed?
If you're trying to publish your site extension to Devops feed and get the feed URL, you can follow this document to do that. Create a Devops feed in Azure Devops Artifacts and then=>Connect to Feed=>Nuget.exe, you can find the url of your Devops feed here:
The format is always https://pkgs.dev.azure.com/OrgName/ProjectName/_packaging/FeedName/nuget/v3/index.json. Maybe this is what you want.
Related
I want to add a custom tab in the Azure DevOps build results page, next to the Summary tab.
Exactly the same questions were asked by different users in 2019. But the sample repo shared is outdated and never updated for more than 5 years.
https://github.com/microsoft/vsts-extension-samples/tree/master/build-results-enhancer
What is the extension points to be used for the same?
All other searches point to the same old repo.
Azure DevOps add custom Tab to Build Summary
Check out the newest documentation on extension development using the Azure DevOps Extension SDK. The new Azure DevOps extension sample uses a new Azure DevOps SDK along with the React-based components in the Azure DevOps UI library described in this site.
Is it possible to run Azure DevOps Web extension when you open any azure devops page?
Probably, there is exists something like "type": "ms.vss-web.azure-load-action" that starts when you open Azure DevOps Website.
In common way, extension contribution runs in a certain scenarios, like - opening hub, opening context menu, etc. Can you run an extension contribution in global context - after azure devops website was opened?
PS. I'he already searched in the VSTS samples, extension points and azure devops extension samples
Thank you, have a nice day!
Unfortunately, extensions don't support "load action". We use extensions to enhance Azure DevOps and Team Foundation Server (TFS) with new web experiences, dashboard widgets, build tasks, and more. You may submit a user voice at website below:
https://developercommunity.visualstudio.com/content/idea/post.html?space=21
I am following the steps outlined here. I am using the Deploy to Azure Extension
https://learn.microsoft.com/en-us/azure/devops/pipelines/targets/deploy-to-azure-vscode?view=azure-devops#github--azure-pipelines
I have done the following steps.
I have managed to create a simple react app and then got the GitHub + GitHub Actions portion to work no problem.
Now, I want to get GitHub Plus Azure Pipeline to work. So, I deleted the GitHub Actions/Workflow files, and starting over with the CICD setup.
Next, I have enabled Use Azure Pipelines for GitHub in the extension.
Then, as per the steps/pictures outlined in the above microsoft documentation link, I have begun the configure CICD option from the command palette.
Selected the Visual Studio Subscription
Selected the target web app
Now, at this point, as per the linked tutorial, it is supposed to ask me to choose a azure devops organization, so that the azure pipeline YAML file can kick in. This step never happens.
instead, VS Code will proceed to generate a GitHub Actions Workflow just as it did before.
What should I do to the GitHub to Azure Pipeline working from this extension?
Update 1
In case anyone is curious, I have raised a issue on the visual studio community forum. You can find that here
https://developercommunity.visualstudio.com/content/problem/1182952/github-azure-pipelines-falls-back-to-github-github.html
As of now, there is an ongoing discussion but no solution yet.
You can try reinstalling Deploy to Azure Extension and enable Use Azure Pipelines for GitHub, and then configure CI/CD option again. If the issue persists, you can report this issue here.
You can create a pipeline directly in your azure devops project. Check out below tutorial
Build, test, and deploy JavaScript and Node.js apps
You will also need to create an Azure Resource Manager service connection to deploy to your azure resource from azure devops pipeline.
Deploy an Azure Web App (Linux)
I want to upload a file to Azure Artifacts using the Rest API. Can I do it?
We use on-prem Azure DevOps Server 2019.
Please, note that it is not a nuget or an npm package. It is just a file.
It is not a nuget or an npm package. It is just a file.
If what you want to upload is files instead of packages, in Azure devops, I'm afraid only Universal package can available for files to stored.
BUT, what the issue is Universal package does not supported for Azure devops server. It only support in azure devops service now.
In our official forum, there has such suggestion raised to request for this feature added in Azure devops server/TFS. You can vote and share your demand there to raise its priority. Our product group will review it regularly to consider take some features into develop plan.
Using the portal:
Using the portal at https://manage.windowsazure.com/ this is easy. From a newly created azure web site:
Go to the dashboard
On the quick glance options on the right, click "Set up deployment from source control"
On the "where is your source code?" option, select Github
Authorize, then choose the repo name and branch.
BINGO: now pushes to that branch will trigger a deployment of that branch onto the azure website. Lovely.
Here's the problem:
I cannot for the life of me see how to do this from the command line (using the xpat-cli installed using npm: "npm install azure-cli -g")
It seems like I should be typing something like:
azure site deployment github --verbose --githubusername [username] --githubrepository [username/reponame] [sitename]
Because the help for "azure site deployment github" says it will: "Link a website to a github account for deployment"
Doesn't seem to work though...
If I then type:
azure site show [sitename]
The output says the source control is "LocalGit" instead of github - which is what it says if I do it the portal way above.
Source Control
data: --------------
data: Type: LocalGit
Any ideas?
Depending on your use case the solution will be different.
Assuming you have the same github source but want to deploy to multiple different Azure websites
Potential Solution: Make use of the Deploy to Azure Button See details here: https://azure.microsoft.com/blog/2014/11/13/deploy-to-azure-button-for-azure-websites-2/
Assuming you have various repositories that you want to deploy to Azure: Potential Solution: I am assuming that you will be the person deploying it. The workflow will be as follows:
A. Download files from Github to local folder See here
B. Publish your local folder into a new/existing Azure site. See here, or here. There are other github repositories to get some scripts right away
I understand this doesnt directly hook your system to do direct pull, but its one way to do it.
There is also:
http://www.imtraum.com/blog/streamline-git-with-powershell/
https://gallery.technet.microsoft.com/scriptcenter/a-GitHub-Repository-265c0b49
Both documents I found describing how to set up continuous deployment from GitHub say that you can configure the repo and branch with an Azure Resource Manager template, but you have to enter your credentials and complete the authorization process in the portal.
The script used in this tutorial will automatically configure
continuous publishing from your GitHub repository. This requires that
your GitHub credentials are already stored in Azure, otherwise the
scripted deployment will fail when attempting to configure source
control settings for the web apps.
To store your GitHub credentials in Azure, create a web app in the
Azure preview portal and configure GitHub deployment. You only need to
do this once.
I'd also suggest posting your xpat-cli problem as an issue on their GitHub repo.