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.
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
I know it's possible to create Logic App in Azure to send message in Teams after completing pipeline. I don't know how can I add hash with completed pipeline as clickable link to open.
I couldn't find any information how can I do this.
I will be grateful for your help.
Azure DevOps Pipelines already have official support to integrate into Microsoft Teams that you could use directly, even without a Logic App.
But if you still need to use a Logic App, then what you could do is use the Invoke a REST API task to call your Logic App, and then send an Adaptive Card which you can design to have a button which links to the pipline.
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.
I created VM for publishing on Azure Marketplace. But I want to test it before I publish it for all. Besides, the publication takes several days.
How to test my offer before publishing on Azure Marketplace?
UPDATE:
I see next screen on Cloud Partner Portal:
Should I publish offer before I can test it?
what you want to test exactly? you can test the ui definition and template separately. you will also have to undergo testing from MS before publication, this readme talks about it in some detail.
You would test template like you normally would.
When you click the Publish button, your offer will be just validated and in preview mode for the subscriptions list you can specify in your offer. This validation takes 40 - 80 minutes.
After that you can send your offer for manual validation by Microsoft engineers, it takes 3-5 days, and your application will be published on Azure Marketplace
hoping someone has seen this before.
When I try to enable continuous integration in Visual Studio, using Visual Studio Team Services, I get the following error:
"This version control host is unsupported. Repositories must be hosted on VSTS or GigHub." This error gets zero results in google.
As you can see in the screenshot, the solution IS hosted by VSTS.
Explaining the screen shot:
Section 1 in the pic is the pop-up that appears after clicking 'Configure Continuous Integration' in the VS2017 status bar.
Section 2 is my VS team explorer window.
The grey boxes are the company website 'mycompany'.
Additional facts:
The VSTS account is owned by admin#mycompany.com, but my dev account, jason#quantumland.com, has full contributor permissions to the project. I get the same error whether red box 1 above has my personal account selected or admin#mycompany.com
The current loaded solution is the basic starter '.NET Core Web application' in VS2017 Community edition. No authentication selected, no changes to the auto-generated code.
I can build and run the solution locally, check in the solution to VSTS, see the code in the VSTS repository, publish to Azure web app, etc. Everything seems to be working but this.
Appreciate any help. My best guess is that my security permissions are wrong in VSTS, but both accounts are members of the 'admin team' group, and admin#mycompany.com is the creator/owner of the VSTS account and repository, so I don't see how.
You are using TFVC version control, the continuous delivery is used for Git version control, so you need to add a new git repository (can be in TFVC team project: Use Git and TFVC repos in the same team project), and use this git repository as source control.
Article about TFVC and Git: Choosing the right version control for your project
I was able to use TFVC for version control and get CI/CD to work. Following the newer instructions provided by #starain-MSFT:
Continuous Integration
This sets up CI/CD using the VSTS web portal exclusively. It works, but if I click 'configure continuous delivery' in the VS2017 status bar and use that form, I continue to get the error above.
If anyone posts an answer that fixes the exact question asked I'll update and mark that as the answer. Good news is that you can indeed use TFVC with CI/CD. yay, and thanks to #starain-MSFT for the updated link.