I LOVE how Microsoft casually assumes that it's normal for your (presumably sensitive, enterprise) application servers to be able to just reach out to any arbitrary node on the internet --- you STILL have to open the firewall -- it's just outbound, not inbound. Unless you're Microsoft and you configure your perimeter firewalls the same way Windows Firewall is configured out of the box (Outbound = Permit All). Good job.
Doubt I'll get an answer on this. But I did this for an old win forms app. I wanted to build and copy the app to an internal server that all devices feed off. I got this working using deployment groups, but every build would overwrite the previous on our server, I tried getting it working so I could store each new build in a new folder name with the latest git commit ID, but no luck. I then looked into doing it with YAML and using Environments. This created the agent service on the target machine, but I haven't been able to actually push the build to the Environment.
YAML and environments are definitely the best way to achieve this. Have you tried altering the physical path of the target server? Maybe use the buildID to create a new folder for each release?
@@AzureDevOps I managed to get it working in the end. I'd never used YAML before so was working it out on the fly and there was no easy option on devops to add what I wanted. Learnt some new things along the way so all good fun :)
I have created CI pipeline and now i want to copy my artifacts and paste in side my Linux server under some directory, But Linux server is Under Firewall for that i have installed azure agent on Linux server and did setup in Deployment Groups. Now agent is showing online on dashboard. Now while creating release, what type of task we can to copy and transfer artifacts on Linux server.
I am trying to deploy code from azure devops to on preme vm or server Is it important to install agent on VM or server before installing Deployment group. Can I use deployment group without installing agent in on preme VM or in server
Hi William! I believe episode 3 goes into that, but check out episodes 2 and 3. Also we have some good docs on this: docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops
@@apriledwards3422 Still trying to get the following working... I have the basic deployment syntax, using it for an approval with human signoffs and an API call. I have an environment (X) with two Virtual Machine resources A & B which means successfully running the powershell on servers A & B. What I'm trying to get to is... A central AzDO agent doing the build stage (got it) with another stage with a deployment job where the agent on the servers A & B deploy to the server that "local" agent is running on.
@@AzureDevOps I'm asking about full YAML. Deployment groups are for "classic" release definitions. Those done via the UI. And actually we figured out this out already after asking the question. We got an AzDO agent installed onto target servers, talking to the central AzDO service. You have to declare an "environment" in AzDO of the target servers with tags describing the servers. From there you need a little more syntax in using "deployment" to use the virtual machines meeting those tags declared in an environment.
The answer here was just a LITTLE more syntax under "deployment" that declared it was virtual machines meeting a certain tag. environment: name: myenv resourceType: VirtualMachine tags: a,b,c
I’m looking for the backend architecture for Azure DevOps data mining. I need to be able to build custom reports to show test results, test development, project development, velocity burnup and burndown, points assigned & completed per employee per release & sprint, etc. etc. Previously I was pulling everything from the On-Prem TFS_Warehouse. If you can point me toward any resource that can provide more details on how to access the necessary data I would appreciate it.
Azure's screens are confusing and YAML sucks! There's a lot of clicking around to find out what does what. It's also a pain to use and adds another unnecessary and cumbersome scripting language in the process.
Awesome. Giving a walk through from requirements angle instead of listing what all ADO can do is the really appreciated
InstaBlaster.
Hi hope you are fine
Hi Ananda
@@morrisdonte8110 Hi Morris
Hi where do you live and how is the weather condition over there today?
I LOVE how Microsoft casually assumes that it's normal for your (presumably sensitive, enterprise) application servers to be able to just reach out to any arbitrary node on the internet --- you STILL have to open the firewall -- it's just outbound, not inbound. Unless you're Microsoft and you configure your perimeter firewalls the same way Windows Firewall is configured out of the box (Outbound = Permit All). Good job.
Doubt I'll get an answer on this. But I did this for an old win forms app. I wanted to build and copy the app to an internal server that all devices feed off. I got this working using deployment groups, but every build would overwrite the previous on our server, I tried getting it working so I could store each new build in a new folder name with the latest git commit ID, but no luck.
I then looked into doing it with YAML and using Environments. This created the agent service on the target machine, but I haven't been able to actually push the build to the Environment.
YAML and environments are definitely the best way to achieve this. Have you tried altering the physical path of the target server? Maybe use the buildID to create a new folder for each release?
@@AzureDevOps I managed to get it working in the end. I'd never used YAML before so was working it out on the fly and there was no easy option on devops to add what I wanted. Learnt some new things along the way so all good fun :)
@@robwalker4653 Learning is always great. Glad you found the answer :)
Diverted from the main topic which was deploying behind firewalls?
I have created CI pipeline and now i want to copy my artifacts and paste in side my Linux server under some directory, But Linux server is Under Firewall for that i have installed azure agent on Linux server and did setup in Deployment Groups. Now agent is showing online on dashboard.
Now while creating release, what type of task we can to copy and transfer artifacts on Linux server.
I am trying to deploy code from azure devops to on preme vm or server
Is it important to install agent on VM or server before installing Deployment group.
Can I use deployment group without installing agent in on preme VM or in server
How do i edit Yaml when i create build pipeline in this way. I am unable to see or change Yaml file
Awesome...
How can i connect to tfs from Visual studio using the server IP ?
Do you have the same video available for how to do this with full pipeline YAML (using what I think would be environment/resources) ?
Hi William! I believe episode 3 goes into that, but check out episodes 2 and 3. Also we have some good docs on this: docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops
@@apriledwards3422 Still trying to get the following working...
I have the basic deployment syntax, using it for an approval with human signoffs and an API call. I have an environment (X) with two Virtual Machine resources A & B which means successfully running the powershell on servers A & B.
What I'm trying to get to is... A central AzDO agent doing the build stage (got it) with another stage with a deployment job where the agent on the servers A & B deploy to the server that "local" agent is running on.
@@williamcthompson7410 Are you trying to chain other servers off A&B? Why not use deployment groups. Sorry, I might be missing the config a bit.
@@AzureDevOps I'm asking about full YAML. Deployment groups are for "classic" release definitions. Those done via the UI.
And actually we figured out this out already after asking the question. We got an AzDO agent installed onto target servers, talking to the central AzDO service. You have to declare an "environment" in AzDO of the target servers with tags describing the servers. From there you need a little more syntax in using "deployment" to use the virtual machines meeting those tags declared in an environment.
The answer here was just a LITTLE more syntax under "deployment" that declared it was virtual machines meeting a certain tag.
environment:
name: myenv
resourceType: VirtualMachine
tags: a,b,c
I’m looking for the backend architecture for Azure DevOps data mining. I need to be able to build custom reports to show test results, test development, project development, velocity burnup and burndown, points assigned & completed per employee per release & sprint, etc. etc. Previously I was pulling everything from the On-Prem TFS_Warehouse.
If you can point me toward any resource that can provide more details on how to access the necessary data I would appreciate it.
Thank you..so, we need to install agent in all machines..right? Does it cost for each agent installed or register to deployment group?
buchepalli ramanareddy it’s free
has anyone tried to install the agent on a 2008 windows server???
Hu Sarah hope you are fine
Thank you! Finally!
It turns out most videos you can find is the CI portion. The CD is till a future promise.
Part 2! what a cliffhanger
Where is part 2? Can someone help me with part 2?
Shiv Shankar Pandit not released yet
ruclips.net/video/58UfRxxAWhE/видео.html
Release part 2 already! 😁
when they tried poking wholes in the firewall they missed and hit your ears...
Azure's screens are confusing and YAML sucks! There's a lot of clicking around to find out what does what. It's also a pain to use and adds another unnecessary and cumbersome scripting language in the process.