Azure-DevOps | Data extraction and Power BI report | Azure library
kandi X-RAY | Azure-DevOps Summary
kandi X-RAY | Azure-DevOps Summary
Code Samples (applications, scripts, PowerBI reports, demos, etc.) to apply on Azure DevOps and GitHub.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Azure-DevOps
Azure-DevOps Key Features
Azure-DevOps Examples and Code Snippets
Community Discussions
Trending Discussions on Azure-DevOps
QUESTION
We have an on premise server (Windows Server 2012 R2) with an Azure Pipelines agent running on it. Today (31st Jan 2022) this agent could not longer connect to our Azure DevOps organisation.
Judging by the log files, I assume this is because it is trying to connect with an older TLS version, which as of today is no longer available - https://devblogs.microsoft.com/devops/azure-devops-services-to-require-tls-1-2/
So I followed the instructions on how to make sure TLS 1.2 was enabled, and confirmed my settings in the registry editor and by running the PowerShell script suggested here - https://docs.microsoft.com/en-us/security/engineering/solving-tls1-problem#update-windows-powershell-scripts-or-related-registry-settings
All seems ok, yet it still fails to connect with the same issue. The machine has been restarted as well. If I try the URL it is requesting in the in built Internet Explorer browser, it fails, but with Chrome it succeeds, so it must still be trying to connect with TLS 1.2, but I don't know why. I've tried reinstalling the agent (with the latest build) as well but it fails on the same error. Any suggestions?
...ANSWER
Answered 2022-Jan-31 at 23:27Enabling below Cyphers with IISCrypto on the server helped us fix the issue
Cipher Suites
TLS 1.2 (suites in server-preferred order) TLS
- _DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 2048 bits FS 256 TLS
- DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 2048 bits FS 128
This from Vijay's solution
QUESTION
Before I start, I've tried all suggestions from the following and none work:
Integration testing ASP.NET Core with .NET Framework - can't find deps.json
https://zimmergren.net/unable-to-find-deps-json-dotnet-azure-devops/
So I'm trying to write some integration tests for dotnet 6. However, my WebApplicationFactory
throws the following error:
System.InvalidOperationException: Can't find '/repos/subscription-info-api/tests/SubscriptionInfoApi.Tests.Integration/bin/Debug/net6.0/...
System.InvalidOperationException Can't find '/repos/subscription-info-api/tests/SubscriptionInfoApi.Tests.Integration/bin/Debug/net6.0/testhost.deps.json'. This file is required for functional tests to run properly. There should be a copy of the file on your source project bin folder. If that is not the case, make sure that the property PreserveCompilationContext is set to true on your project file. E.g 'true'. For functional tests to work they need to either run from the build output folder or the testhost.deps.json file from your application's output directory must be copied to the folder where the tests are running on. A common cause for this error is having shadow copying enabled when the tests run. at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory
1.EnsureDepsFile() at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory
1.EnsureServer() at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory1.CreateDefaultClient(DelegatingHandler[] handlers) at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory
1.CreateDefaultClient(Uri baseAddress, DelegatingHandler[] handlers) at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory1.CreateClient(WebApplicationFactoryClientOptions options) at Microsoft.AspNetCore.Mvc.Testing.WebApplicationFactory
1.CreateClient() at SubscriptionInfoApi.Tests.Integration.UnitTest1.Test1() in /repos/subscription-info-api/tests/SubscriptionInfoApi.Tests.Integration/UnitTest1.cs:line 14 at SubscriptionInfoApi.Tests.Integration.UnitTest1.Test1() in /repos/subscription-info-api/tests/SubscriptionInfoApi.Tests.Integration/UnitTest1.cs:line 16 at Xunit.Sdk.TestInvoker1.<>c__DisplayClass48_0.<b__1>d.MoveNext() in /_/src/xunit.execution/Sdk/Frameworks/Runners/TestInvoker.cs:line 264 --- End of stack trace from previous location --- at Xunit.Sdk.ExecutionTimer.AggregateAsync(Func
1 asyncAction) in //src/xunit.execution/Sdk/Frameworks/ExecutionTimer.cs:line 48 at Xunit.Sdk.ExceptionAggregator.RunAsync(Func`1 code) in //src/xunit.core/Sdk/ExceptionAggregator.cs:line 90
My actual test code is extremely simple:
...ANSWER
Answered 2021-Nov-18 at 21:03You are probably targeting the wrong namespace for Program in your test file (like I was).
I had to add the following at the end of my Program.cs file (last line) to make it visible to my test projects needing it:
QUESTION
Hi i am trying to get code coverage with .net5 in azure pipeline.
Run tests (not entire file)
...ANSWER
Answered 2021-Aug-25 at 08:52Please replace your PublishCodeCoverageResults
with following steps:
QUESTION
I'm attempting to use Azure DevOps Services Rest API to create a new branch from master but I've been unsuccessful.
Body:
...ANSWER
Answered 2022-Jan-13 at 20:41newObjectId
is the object id of the existing branch. Really not sure why this is named new when it is actually older. Very odd.
QUESTION
We have a CD/CI Azure Devops build pipeline that has started failing for nodejs/node-gyp
.
error gyp info using node-gyp@3.8.0
error gyp info using node@16.13.0 | win32 | x64
Nothing about our build pipeline has changed, the pool we use is:
...ANSWER
Answered 2021-Dec-13 at 09:42Azure auto updated the version of node it was using, pushing the required version of node-gyp forward too, this lead to all of our builds failing. The versions it pushed to were:
- npm@8.1.0
- node@v16.13.0
Add task: NodeTool@0
to set the Node version to the last passed version which for us was:
- npm@6.14.15
- node@14.18.1
The end code looks like this:
QUESTION
In the documentation for conditions in Azure DevOps pipelines the following example is given:
...ANSWER
Answered 2021-Dec-14 at 10:16This example is titled as "Run if the build is scheduled, even if failing, even if canceled".
So, this condition:
QUESTION
Update:
Is it possible to add or change a command that executes a pipeline on Azure DevOps?
Running my program locally on Visual Studio Code, I do get outputs.
However, running my GitHub origin branch on Azure DevOps does not yield any output.
I followed a Stack Overflow answer, which references this solution to a GitHub Issue.
I have implemented the below, but Azure's Raw Logs return blank on my Python logging
.
test_logging.py
:
ANSWER
Answered 2021-Oct-18 at 12:18I think you have fundamentally mixed up some things here: the links you have provided and are following provide guidance on setting up logging in Azure Functions. However, you appear to be talking about logging in Azure Pipelines, which is an entirely different thing. So just to be clear:
Azure Pipelines run the build and deployment jobs that deploy the code you might have on your GitHub repository to Azure Functions. Pipelines are executed in Azure Pipelines agents, that can be either Microsoft- or Self-hosted. If we assume that you are executing your pipelines with Microsoft-Hosted agents, you should not assume that these agents have any capabilities that Azure Functions might have (nor that you should execute code aimed for Azure Functions in the first place). If you want do execute python code in your pipeline, you should first start looking at what python-related capabilities the hosted agents have pre-installed and work from there: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
If you want to log something about pipeline run, you should first check the "Enable system diagnostics" option when queuing pipeline manually. For implementing more logging by yourself, do check: https://docs.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash
For logging in Azure Functions you might want to start here: https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring , but that would be an entirely different topic than logging in Azure Pipelines.
QUESTION
I installed Azure DevOps Server 2020.1.1 (Product Version: 18.181.31527.1, ADS 2020 Update 1.1, Release date: 8/17/2021) on an application server and configured it successfully. My security guy ran a Nessus vulnerability scan and Nessus reports that the app server fails Security Updates for Microsoft Team Foundation Server and Azure DevOps Server (April 2021) (Nessus vulnerability check #148714). In other words, it seems I need to install a patch from April 2021 for ADS 2020 Update 0.1 to cure a vulnerability for ADS 2020 Update 1.1 released in August 2021
The Nessus solution says this:
Microsoft has released the following updates:
- Azure DevOps Server 2019 Update 1.1 with patch 8
- Azure DevOps Server 2020 Update 0.1 with patch 2
Additionally, Team Foundation Server 2017 Update 3.1 through Azure DevOps 2020.0.1 require resource group task(s) to be manually applied.
So, this Nessus description says the fix for my ADS 2020 instance is to apply Azure DevOps Server 2020 Update 0.1 patch 2 and it provides a link to April patches for Azure DevOps Server and Team Foundation Server. The description for ADS 2020 0.1 with patch 2 includes VERY involved tasks AzureResourceGroupDeploymentV2
and AzureResourceGroupDeploymentV3
.
Why would a version of ADS 2020 released August 2021 require patches published for a prior version of ADS 2020. This makes no sense.
p.s. I put this same question on the Microsoft Developer Community board 3 weeks ago but have not received an answer/solution
...ANSWER
Answered 2021-Oct-08 at 07:50Microsoft has performed a re-release of the 2020.1.1 version with an increased version number; 18.181.31527.1. The solution is to repair the Azure DevOps installation, then update to the re-release version and then apply patch 1. I have a full overview of all versions of Azure DevOps Server and TFS (https://github.com/FokkoVeegens/AzureDevOpsServerVersions), which I will update accordingly, so thanks for your question ;).
QUESTION
In repo-A have an Azure DevOps pipeline which is executing a Powershell script, which in turn does various git commands in order to mirror an external repository and push it to repo-B.
The Powershell script resides on a self-hosted agent:
...ANSWER
Answered 2021-Oct-06 at 01:50The issue was resolved by a combination of two things (refer to this question for further detail):
Adding a Personal Access Token with the Code Read & Write permission enabled
Using the PAT in the url of the git push:
git push https://{PAT}@dev.azure.com/{organization}/{project}/_git/{repo-name}
QUESTION
My pull request has conflicts but I can not find anywhere to resolve them in either DevOps or VS2019
There is More Actions Tool Tip
Here are the actions
The docs indicate that VS2019 has some Pull Request features but I cannot see them in Team Explorer or under the Git menu
In VS2019 in the Git Changes tab, working in the fork that the pull request is for, when I pull I get a message that the repository is already up to date.
The Pull Request is from Master of the repository to Master of a fork.
...ANSWER
Answered 2021-Sep-14 at 06:27You won't be able to resolve merge conflicts directly within Azure DevOps. But you can resolve them with e. g. Visual Studio or using a command line.
This is the documentation you are looking for: Resolve merge conflicts
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Azure-DevOps
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page