How to enable TaskO in Azure DevOps - azure-devops

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.

Related

How to use ClickOnce custom prerequisites with Azure DevOps Pipelines

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.

Adding a new tab with HTML content in Azure DevOps build result

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.

Run Azure DevOps extension in the background

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

Deploy to Azure Extension - Only Allows Creation of Github Actions Workflow. Wont Allow GitHub + Azure Pipelines Flow Creation

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)

Will the Team Retrospective extension have a more permanent replacement with the Azure Devops platform?

My team uses the Team Retrospective extension & it's being un-published from the marketplace later this month. I'd love to know if Azure Devops will continue to support this extension and/or if it will be replaced as a new feature within the Azure Devops platform.
I'd love to know if Azure Devops will continue to support this extension and/or if it will be replaced as a new feature within the Azure Devops platform.
AFAIK, Azure Devops will continue to support this extension. I got following message:
Retrospectives will be un-published from the Marketplace on May 29,
2020 Beginning on May 29th, 2020 the Team Retrospectives extension
will no longer be available on the Azure DevOps Marketplace. Existing
installations will continue to work with the exception of the
real-time update feature, until your organization admin explicitly
removes the extension from the ADO tenant. Thank you to everyone who
provided feedback for helping to improve the extension ecosystem.
So, if you have already installed this extension on your organization, it will continue to be supported.
Hope this helps.