I have yaml pipeline in Azure Devops. Simple tasks such as building a project and running unit tests are taking 10 times longer today than they were. I'm in Europe and I can see that the Artifacts service is degraded. Would this explain the slow build and does anyone know a work-around such as a way to force the build agent to run in a different region?
https://status.dev.azure.com/
The issue seems is related to the following Azure DevOps Incidents:
https://status.dev.azure.com/_event/233282345
https://status.dev.azure.com/_event/233249026
https://status.dev.azure.com/_event/233260207
Please try as the workaround mentioned in the Incident, adding the self-hosted agents to run your pipelines.
Now all regions have the problem with pipelines:
Related
Opened this query in MS Developer Community Forum / Azure DevOps issue
https://developercommunity.visualstudio.com/t/No-agent-found-in-pool-Default-which-sat/10141890?space=21&q=gtversion&entry=problem
Trying to work out why the "Pipeline" runs successfully with my self-hosted docker agent but the "Release Pipeline" fails, it's asking for a version way under the version of the agent I am running
“No agent found in pool Default which satisfies the specified demands: azureps, Agent.Version -gtVersion 2.144.0”
Any given help will be very much appreciated
Compromised installing the PS AzureRM module necessary for the release pipeline tasks to run, and added two user-defined capabilities to the agent to overcome the initial error
Documented the "solution" here
https://developercommunity.visualstudio.com/t/No-agent-found-in-pool-Default-which-sat/10141890
When using Azure DevOps I notice that occasionally my pull request builds will fail. After some tracking down I noticed that this is only happening when another build is already running.
It seems that the reason is that the files in the output for the build (exe, dll, note_modules, etc.) will be locked so when another build is started the new build will fail until the currently running one is finished, then I will have to manually re-queue the build again.
I am not very familiar with Azure DevOps pipelines since we recently migrated to this platform and also not sure of the best way to fix this issue. The sln's being built include .NET Framework, .NET Core, TypeScript, and Node.js if that helps at all.
I would love to post the logs and current configuration, but due to company policy I'm not allowed to... :(
Azure DevOps build pipelines fail when another build is already running
You could try to use/add a Capability, like Agent.Name to that two specific build agents then in the build definition you put that capability as a Demands.
As stated here:
How to send TFS build to a specific agent or server
The Capabilities of the agent:
Project Settings->Agent pools->Your agent pool-> Agents->Agent->Capabilities
The Demands of the build pipeline:
Options-> Demands:
In this case, when a pipeline is running in this particular agent, another new build will be in pending state until the current build is completed.
We have been using a YAML file to do our CI in Azure DevOps for a few months with the idea that we would get our release configured using YAML in the future.
Well that time is now and I'm confused by how you would introduce a CD process. With the MyProject-CI.yml being a Build Pipeline and our Releases being Classic Pipelines I assumed that when the time came to get the CD process down as YAML we would create a MyProject-CD.yml. That would be triggered by the dropping of an Artifact within the MyProject-CI.yml CI.
However I think that was just a misunderstanding on my behalf and what we are supposed to do is convert the original MyProject-CI.yml into a multi-stage pipeline that has the following stages
Build and Run Unit Tests
Deploy to Development and run WebTests
Deploy to Production and run WebTests
Is the switch to a multi stage CI/CD in one file correct rtaher than Release and Build in separate files?
The short answer is yes, you got the idea. A single multi-stage pipeline yml is the way to do both build and deploy, and that is the base intention. Here is an exercise that parallels your case that might help.
As your pipelines get more complex, you will likely get into scenarios with multiple files, as you can template parts of your pipeline for reuse in multiple places, or to enforce conventions from a central location.
I am trying to run a release pipeline which contains different stages for different sections of the website. However one of the stages throws an error when downloading the artifact. The other stages work as expected.
Error:
##[error]One or more errors occurred. (Dedup size does not match the downloaded size.
I cannot find anything only that explains to me what Dedup is with regards to Azure Pipelines
This issue seems relevant with the recently event on Azure Devops. In addition, this issue is more for agent.
If this issue occurred on what you are using is Hosted agent, just change to using your private agent to finish the release pipeline. Besides, if you are using private agent, please ensure the version of agent you are using is the latest one: 2.155.1.
Summary
Recently migrated PB126 apps to PB2017 and changed source control to Azure DevOps Git.
Now, I'd like to integrate Azure DevOps CI/CD Build Pipeline to the app dev life-cycle.
jenkins
I know it's feasible to configure jenkins CI server so it builds PB2017 projects.
Continuous Integration with PowerBuilder 2017, Bonobo Git and Jenkins
My problem here's I can't get it to work on a local Docker container and make it accessible to the outside world (Internet) so Azure DevOps can trigger its build action. Supposedly, it's a Docker for Windows thing which Docker handles differently from the Linux-based Docker.
Azure DevOps Pipeline
As per this link, Azure Pipelines is the CI/CD solution for any language, any platform, any cloud, it says any language, which makes me believe it's feasible to build PB2017 projects using Azure DevOps Pipelines.
The fact is that I'm totally new to CI/CD in terms of implementing it myself. I've experienced it in many projects where I wasn't responsible to implement it. Now I am. I've been on it since a few days now, and I do want it to work.
Any help appreciated.
The Appeon offical user forum: https://community.appeon.com/index.php/qna/q-a