devops-service | DevOps Service is the core service | Microservice library

I'm a newbie to Azure

I created a new Vue project using vue create which runs locally and even serving the dist folder too it run successfully. (serve -s dist)

And then I deployed the application using GitActions to Azure(Web App Service) which Azure DevOps services indicated that the deployment has been successful: azure-devops-service-github-actions

So I was expecting to see the default page as: vue-app-default-page-content

Instead, it still shows as: azure-site-landing-page

There are no error messages, and I'm not sure how best to debug what has gone wrong with a deployment. Also not sure if later when I use the application with any REST APIs does it include any configurations to get it up and running.

Secondly, not a blocker, but after removing these lines from the workflow - master.yml file the deployment continued without any issue. Used Node 12 and Node 14. I Googled and have no idea why??

I built a Scale Set(Windows) and I can run simple commands successfully on my Azure Devops Custom Agent Pool, with a custom VM based on Windows 19 Server Core based on this guide.

However, when I try to access any Azure Devops predefined variables in any of my tasks they are not recognised. For example executing:

Hoping someone can help me with this as looking back at my git log I've now tried 14 different things to try to get this to work. Here's the scenario:

• I created a variable in the UI called deploy_custom_env and checked "User can set variable at runtime." I initialized it to "default", but I am expecting users to override it when starting manual runs.

• I am trying to use this variable in the condition for some of my pipeline stages.

• I've tried many, many different things. Here are some examples:

First:

In Azure Pipeline is possible use predefined build variables (DevOps Services) Build.SourceBranch and Build.SourceBranchName but their values at case commit with tag are tags.

In doc. https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#build-variables-devops-services is written

• When your pipeline is triggered by a tag: refs/tags/your-tag-name
• The name of the branch in the triggering repo the build was queued for. Git repo branch or pull request: The last path segment in the ref. For example, in refs/heads/master this value is master. In refs/heads/feature/tools this value is tools.

• this my observation: but in case commit with tag is the last path segment of Build.SourceBranch, so your-tag-name

Could someone throw some light on the difference between basic and Visual Studio professional subscription access levels in Azure DevOps?

Microsoft document here provides abstract information regarding the different access levels.

We have few users who are tagged with basic access level (who also have Visual Studio Professional Subscription) while few other users with Visual Studio professional subscription.

It is understood from this link that basic access level subscription billed $6 per month, the question that arises now is if azure devops is available for usage without cost if the user has visual studio professional subscription, and do we need to buy basic access level for users who do not have Visual studio professional subscription.

I'm trying to create reporting against work items in Azure DevOps from PowerBI for my entire organization. But I don't have access to all of the projects, so the odata connector returns an error. (per the last statement on https://docs.microsoft.com/en-us/azure/devops/report/powerbi/analytics-security?view=azure-devops)

Can I use a different PAT through Power BI? I don't see a way to do this.

I tried following the answer from How do you get DimIteration table information from Azure Devops Services into Power BI? with a PAT I was given and a variety of URLS, but did not work.

And I'm using Power BI (not writing C#, Java, etc.), so I don't see where the Authentication Guide fits into my solution.

The Add a dashboard widget tutorial explains how to call the work item REST API using a VSS.require("TFS/WorkItemTracking/RestClient")d rest client.

I want to do the same, but for the Wiki Rest API. There certainly is a scope for this: vso.wiki.

However, I cannot find the equivalent of "TFS/WorkItemTracking/RestClient" for wiki. Maybe it is as simple as "TFS/Wiki/RestClient", but even if it was, what are the names and parameters of the functions I can use? I don't find that documented anywhere, and I don't want to have to figure that out by trial-and-error, each time publishing a new extension and seeing if it works.

And looking at REST Clients, there does not even seem to be a Wiki Rest Client.

So how can I access the Wiki Rest API from an Azure DevOps extension? Is there perhaps an example somewhere, that google has been successful in hiding from me?

N.B. I do know about the REST API Specs, but the mapping to REST client is not self-evident and apparently.

I stumbled upon Azure DevOps Web API clients and contracts, however, a brief grep revealed it does not contain the latest and greatest (pre-release) "pagesBatch" feature, and I did not find a relevant branch / tag either.

I have over 100 YAML files within an existing Git repo, each defining their own build pipeline. I am trying to create a PowerShell script to create these build definitions so I don't have to spend hours using the web UI to manually add new build definitions and point to their respective YAML files.

I've come across similar questions and resources, but haven't been able to get this script to work.

• How to create Build Definitions through VSTS REST API
• Create Build Definition using Azure Devops API
• https://www.nebbiatech.com/2018/11/29/automating-build-pipeline-creation-using-azure-devops-services-rest-api/

I know the REST API documentation supports cloning, but does it support creating a build definition that links to a YAML file within the Git repo?

I am using Azure DevOps Server 2019 (ADOS for short, installed on-premises) to run end to end tests based on Selenium in C#.

Every now and then a build ends badly without properly stopping the chromedriver.exe process used by my Selenium tests. As a result, the subsequent build fails at the Initialize Job step with an error that looks like this:

One or more errors occurred. (Access to path 'C:...\chromedriver.exe' is denied.)

What I understand from this is that because chromedriver.exe is still running ADOS cannot delete its .exe file when it tries to clean the working folder at the start of the build run.

I've tried disabling the Clean feature of the Get sources step definition but that only shifted the error a bit forward to the Checkout step.

To resolve the problem I am forced to manually RDP into my agent machine, taskkill /IM chromedriver.exe /F and re-run the failed build.

My question is - How can I prevent the access denied error? I've thought of these approaches but I'm not sure which is practical:

1. Get ADOS to run taskkill automatically before the Get sources step. How?

2. Make the agent have higher privileges so it can delete chromedriver.exe even when its process is still running. Again, how?