I need to customise vsts build summary by adding a chart(a pie chart and a bar chart) for which the data source will be azure blob or a local csv file generated after the build execution.
Do we have any default vsts tasks available or
writing vsts extensions is the only way out of this.
There is not any built-in official task or extension could achieve your needs. You could go through Visual Studio Team Services Marketplace if there are some 3rd-party extension meet your requirement.
You want to build an extension for VSTS and Microsoft has created a GitHub repo with a number of samples and reading material to get you started. Otherwise, you may have to write your own extension, some tutorials for your reference:
VSTS Extensions Samples
Develop Extensions for VSTS
As for how to accessing Azure Storage from a VSTS extension, take a look at this blog.
Related
We have a ClickOnce application we try to deploy with Azure DevOps pipelines.
We have figured the deployment process out with creating manifests and signing them.
The problem is now we want to also use the prerequisits option of ClickOnce with some custom packages.
After reading the docs we created a custom bootstrapper package and it was displayed in Visual Studio. When we publish the app with Visual Studio the custom package is added. But if we use it on the DevOps pipelin it's ignored. This makes sense because the build server doesn't know the custom package.
For example one prerequisit is the Microsoft OLE DB Driver for SQL Server.
One Idea maybe would be to not use the option "Download prerequisites from the component vendor's web site", but host the exe/msi files ourselves and link to them.
Another option could be this support URL for individual prerequisites but here I don't know how to set this to other applications.
Does somebody have an idea how custom prerequisites with ClickOnce can be added to a Azure DevOps build server/pipeline?
You could try to use Azure cli to upload the package(with its setup.bin file) to Azure DevOps artifact feeds
as universal packages type.
Create a feed first then you could use az artifacts universal publish to upload the packages.
Then you could use the "Universal packages" task in your Azure DevOps pielines to download the packages for using.
As you said, you could use visual studio run with the packages successfully. If you use VSBuild#1 task as the doc recommend in your pipelines to deploy the ClickOnce, you could add the path of the custom package in Azure DevOps, it looks like something like this:
'p:GenerateBootstrapperSdkPath=$(System.DefaultWorkingDirectory)\bootstrapper'
I hope it could help.
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 installed the TaskO extension for my Azure DevOps organization. However, when I open one of my projects that uses the Scrum or Agile process I do not see where to create the automated tasks. Does anyone know how to create tasks with this extension?
Following TaskO UI is shown for each project. You can add tasks to the project, edit and delete them. These work as templates for actual tasks which are created by Azure DevOps whenever you add requirement/user story/PBI. You can also see the button to add the tasks for existing requirements. This TaskO UI is not required to be used after you have defined the tasks for that project. Creation of the actual tasks works in the background.
How to enable TaskO in Azure DevOps
I am afraid this TaskO extension is not very compatible with Azure Devops. I have installed this extension successfully for a long time, but I still could not make it work for my Azure Devops.
After install that extension for my Azure DevOps account, I could not see any add tasks UI display on my Azure DevOps. And on the page Q & A, there is also some feedback that they are not able to use this extension properly.
Besides, I have found a similar extension TaskO 2015, which is only work for TFS 2015. I am not very sure if this extension is work with Azure Deops. If this extension is work with Azure Devops, #Gouri S may need to provide us detailed instructions, which could help us to use this extension.
Hope this helps.
I am doing some research for Powerapps integration with Azure DevOps.
However there is limitated information for it.
It is possible to integrate powerapps inside a Task for AzureDevops?
Based on, that we have a .zip file with the Powerapp, and we want to create a Build and Release/Deploy for several environments.
Thank You.
It is possible to integrate powerapps inside a Task for AzureDevops?
Yes it is.
You can leverage the Solution concept of the Microsoft Power Platform and the Power Apps BuildTools (preview) extension for Azure DevOps.
Update 11/2020: This is now GA and called Power Platform Build Tools
I've written a complete step-by-step guide on this topic:
A Continuous Delivery Approach for No-Code Solutions in Microsoft’s Power Platform
Bottom line:
With this build tool, you can automatically check-in a Solution into source control and deploy it using a continuous delivery approach with the help of Azure DevOps. See the screenshot for a sample configuration of the Export and Import Solution Task.
It works for everything you can organize inside a Solution, e.g.:
Power Apps
Power Automate Flows
AI Builder Models
Common Data Service Entities
It is possible to integrate powerapps inside a Task for AzureDevops?
I am afraid there is no such Task integrate powerapps for AzureDevops at this moment.
If you want to integrate powerapps with azure devops, you can follow the guide step by step:
Microsoft Teams – Integration with Visual Studio Team Services using PowerApps.
Besides, AFAIK, PowerApps should not be "Build/Deployed" through Azure Devops.
When you are developing with PowerApps, there is no way to do Source
Control. There are no source files. The only artifact you can version
control is the .zip file that you can export.
And
In PowerApps, you don’t have to build your code. Any change you make
to the application is live for you to test it. In that way it is very
productive. To publish the application you just click on the publish
button and it is live.
Check this great blog: PowerApps From A DevOps Perspective for some more details.
Hope this helps.
Solutions are a way to package your components in a single zip file and use Powerapps build tools to import your solution on to a different environment or tenant.
It is still a an improvement from manually importing each app or environment variable and then import it on to target system, but it lacks what we call as automation of deployment.
To provide an eg, I will explain what I have done, and what still constitutes of a manual task:
I created an enterprise level app using powerapp canvas model. My app consumes data from around 20 APIs. These API calls are implemented in power automate.
We have 4 environments, dev, sit, uat and prod. Now I cant keep on importing flows in each environment and change their api URLs to point to the deployed environment. So I used environment variables for each environment which stores api URLs for each environment. This can be done under solution.
Under the same solution, I added my app. So now my solution has 2 things, my app and the environment variable which consists of api URLs.
I then use powerapps build tools to move this solution from dev to sit.
Steps: use build tools tasks to perform the following
Export solution
Unpack it in git
Pack it
Import the solution.
This successfully moves my solution to sit.
But the solution environment variable still points to the dev url.
So I have to override environment variables to store sit URLs.
This manual intervention to edit environment variable is as good as doing all the tasks manually.
This was the case when PowerApps was first announced; however, this is no longer the case.
While it is technically true that there is no actual code that would be managed and deployed with a PowerApp or Flow but that doesn't mean that you can not use the power of Azure DevOps. Additionally, when creating a PowerApp / flow you would also be creating entities and even Model Driven apps - and these uses solutions - which naturally work well to deplooy within Azure DevOps.
Microsoft is building out this whole construct to enable all these to deploy...
While the whole incorporation of PowerApps and flows into Solutions is not fully baked yet - they are targeting to have this ready around the October time frame this year.
We have been talking to Microsoft about also enabling PowerApps and flows to follow the same expansion that solutions do so that they can take advantage of the full branching strategy.
So even though you would be simply exporting out zip files into your repo - you can still take advantage of the full devops pipeline which is highly recommended.
Use this component, it still on preview mode but is working fine on my side
https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools