I'm building a project in Azure Classic pipeline.
now i have to publish an HTML File to the tab, so i used one or more extensions (Publish HTML Reports, HTML Viewer).
The problem is, it doesn't publish css scripts, so that the published page is not viewing perfectly.
This is what i want 👇👇
This is what i got 👇👇
Source code of both images are not same, used for better understanding
I am afraid Azure devops doesn't support publish custom HTML report yet.
There are user voices having been submitted to Microsoft development team. See user voice Support for generic HTML Publishing inside Build and Release Pipelines.
You can vote up above user voice, Or create a new user voice of your own regarding this issue.
Related
In below image I can see that there are multiple tabs when we create pull request like Overview, Files, Update, Commits, etc. I want to add a new tab in pull request. I tried searching on internet but was not able to find much. It will be great if someone can help me with it.
Thank you
I agree with #4c74356b41 AFAIK that's not possible without creating a full-blown extension\addon.
Reference taken from :
Azure DevOps-Add extension that adds custom tab to Pipeline / Release Definition page (not the summary page) - Stack Overflow
. I don't know the term I should use to search for it.I am just not sure what to search in google to learn more about it.
you can search for the following terms on Google :
Azure DevOps extension samples
Azure DevOps extension custom tab
Azure Devops Extensions Overview
I am ok with adding addon\extension. I actually want to know some document references that can be useful in this scenario
As you are ok with extension you can refer this MS document Extensions overview.
To create a new tab in a pull request, you need to create an extension that adds the new functionality to Azure DevOps. You can use Visual Studio to create a new Azure DevOps extension project.
Reference for Working with Pull Requests in Visual Studio Code and Azure DevOps
Reference SO thread
Using Azure DevOps, I'm trying to build an extension with widget that can retrieve any open source API (e.g., weather API for example). This is a step-by-step process that I've come up with to build that extension/widget:
Choose a weather API to use, for example OpenWeatherMap API, and obtain an API key.
Create an Azure DevOps extension project using a code editor, such as Visual Studio Code.
Add the required dependencies to your project, such as "vss-web-extension-sdk" and "axios".
Create an HTML file for the widget layout, and add a placeholder for the weather data.
Write JavaScript code to fetch the weather data using axios and the API key.
Use the VSS SDK to create a widget and bind it to the HTML file.
Test the widget in the Azure DevOps extension host.
Package the extension and publish it to the Azure DevOps Marketplace.
Based on the available ADO extension widgets, I'm certain that ADO can access any API data without any issue, but I'm struggling to find any proper training materials to do this. Does anyone know if Microsoft provides any sort of guideline to access OpenWeatherAPI or other open source APIs?
I need to capture image form publish test result and that captured image needs to send in an email.
is this possible in Azure DevOps ci/cd pipeline?
I have attached below screenshot for reference.
Please help me.
This is not available as an out of the box feature as of today, AFAIK. At most, you can see the stats of the latest test run included in the build completion email notification with a link to the see them on the Portal.
However, you can search for suitable Azure DevOps extensions in the Visual Studio Marketplace, or submit your suggestion at the Developer Community for Azure DevOps for our Team to look at.
I am migrating from TFS 2015 to Azure DevOps. The process of creating the target project and importing the old git repository can easily be done through the Azure DevOps API.
But each new project, either created manually or by API has always all services (Boards, Pipelines, Test Lab, ...) enabled. Is there a way to change the default setting of which services should be enabled on new projects? Or even better an API method to switch certain services on / off?
We have hunderets of projects and therefor it's not feasible to open each project in the browser, change to the project settings page and adjust the services.
I haven't found anything in the docs: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-5.0
This guy wrote a blog post on how to do this
This is an excerpt pulled from his post:
PATCH https://{account}.visualstudio.com/_apis/FeatureManagement/FeatureStates/host/project/{project-id}/{feature-id}?api-version='4.1-preview.1'
content-type: application/json
{"featureId":"{feature-id}","scope":{"settingScope":"project","userScoped":false},"state":0}
Replace account,project-id and feature-id as appropriate. Here are the feature id’s I know of.
ms.vss-build.pipelines [Azure Pipelines]
ms.vss-test-web.test [Test Plans]
ms.vss-work.agile [Azure Boards]
ms.vss-code.version-control [Azure Repos]
ms.feed.feed [Azure Artifacts]
It looks like turning a service off really just means hiding it from the UI.
Edit: it looks like the .net SDK has built in support for this as well
We are migrating our DocuSign Demo account to production. For this- we downloaded all templates from demo account as xml and uploaded same on production account- Which is working fine.
We have approx 200 custom Tabs created for these templates in demo account, is there any way to download/migrate these Custom Tabs to production account?
Good question, unfortunately there is no way of completely automating this; however there's one important thing I'll mention here which implies that you might not even have to migrate any of your Custom Tags, and I also have a manual workaround that will save you time if you do indeed want to migrate them.
First off, if you're using Custom Tags in templates only then you probably don't need to migrate any tags. The custom tag definition is embedded within the xml of your templates, so the system should have enough information to display and utilize them in your envelopes as expected.
However if you're using them in other places and/or you want them to show in the Custom Tag area of your production account preferences in order to modify them, then you can do the following to help save some time:
Create and save a template in demo that has all the Custom Tags that you want to migrate.
Migrate the template by downloading the template xml from demo and uploading into your production account.
Open the template and for each tab you want migrated double click and select Save As Custom. This will in turn add the Custom Tag to your production account.
Unfortunately that's the quickest way to migrate Custom Tags currently, but as mentioned you might not have to do this at all - your envelopes still have all the info they need to function properly in production.