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.
Related
I want to develop an azure devops web extension under the test plans
navigation menu.
I would like to have a configuration page (one text
box for input and button for submit). This configuration page must be
launched during the installation of the extension and this page
should not be accessed from test plans
How can I do the configuration in Azure devops extension?
How to add a configuration during Azure DEVOPS web extension installation?
I am afraid there is no such configuration in Azure devops extension to add a configuration page during Azure DEVOPS web extension installation.
You could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
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 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.
We are trying to set up the Team Services to Zendesk app, but we are getting an error when we try to upload it into Zendesk, "Missing required key from translations/en.json: app.name". Anyone else gone through the uploading of this App, or have an idea of what we may need to do to overcome this error.
It’s caused by the Zendesk Apps framework (ZAF) V1 hasn’t been supported by Zendesk since Aug 1st 2017.
Beginning August 1st, 2017, Zendesk will no longer permit uploads of
new private apps using the v1 framework.
Learn more
To upload the private app (*.zip) to Zendesk, you should use framework v2.
I posted an issue to suggested change the code for vsts-zendesk-app with Zendesk Apps framework v2 correspondingly, you can follow up.
The work around for now is migrate farmework from v1 to v2 manually. You can refer Migrating to v2 for details.
try this app
https://www.zendesk.com/apps/support/integratecloud-connector-for-vsts/?q=mkp_vsts
Azure DevOps (VSTS) Integration App by IntegrateCloud, allows the users to create Azure DevOps (VSTS) work items right inside the Zendesk form. It also allows you to link existing Zendesk tickets to an existing Azure DevOps (VSTS) work items. In addition, it allows Agents to notify the Azure DevOps (VSTS) team, by sending comments inside Zendesk Support.
We also support customization based on customer request and tailored to your needs! We bring Azure DevOps (VSTS) closer to your business model!
The App has 5 buttons, 'New Work Item', 'Link Issue', 'Link to Work Item', 'Notify' & 'Show Item Comments'.
-New Work Item: When clicked on the New Work Item tab, select the type of work item you want to create Bug, Epic, Feature, Task, User Story etc. Based on the selection it will load all the Azure DevOps (VSTS) fields. The User can make the selection and click on Create button which would create work item in Azure DevOps (VSTS) and then display the corresponding Azure DevOps (VSTS) work item Id in the App.
-Link to Work Item: This tab allows you to link an existing Zendesk Ticket. It can be linked to one work item in Azure DevOps (VSTS) .
-Notify: This tab allows the user to send notifications to the Azure DevOps (VSTS) team which would show up as comments in Azure DevOps (VSTS) .
-Show Item Comments: This tab shows you all the linked Azure DevOps (VSTS) work item comments log to current Zendesk ticket.