-
Git v/s TFVC
I found one nice artical talking about Git v/s TFVC and think it’s worth to share.
Git (distributed)
Git is a distributed version control system. Each developer has a copy of the source repository on their dev machine. Developers can commit each set of changes on their dev machine and perform version control operations such as history and compare without a network connection. Branches are lightweight. When you need to switch contexts, you can create a private local branch. You can quickly switch from one branch to another to pivot among different variations of your codebase. Later, you can merge, publish, or dispose of the branch
TFVC (centralized)
Team Foundation Version Control (TFVC) is a centralized version control system. Typically, team members have only one version of each file on their dev machines. Historical data is maintained only on the server. Branches are path-based and created on the server.
-
Git with VSTS - Part 2- Git Repo
Depending upon the requirement you can have one or more repo inside your project. You can create repos by using
1. Web (VSTS) 2. CLI 3. Visual Studio 4. IntelliJ 5. Xcode 6. Eclipse
-
PowerShell to find service availability across the regions
It’s always good to have pre-flight validation check. Many time we have face the problem where end customer is deploying service/s which is not available to desired region. Output of the below script return the regions where the particular service.
-
Git with VSTS - Part 1
VSTS or Team services offers 2 types of version control 1. Git 2. TFVC
Git is a distributed version control system. Each developer has a copy of the source repository on their dev machine. Developers can commit each set of changes on their dev machine and perform version control operations such as history and compare without a network connection. Branches are lightweight. When you need to switch contexts, you can create a private local branch. You can quickly switch from one branch to another to pivot among different variations of your codebase. Later, you can merge, publish, or dispose of the branch.
-
PowerShell Desired State Configuration - Part 1
Configuration Management
“Configuration management (CM) is a system engineering process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design, and operational information throughout its life.”
-
IaC - ARM Templates Fundamentals
With the introduction of Azure Resource Manager model life become much easier. New model not only provide much more granule control over design, deployment and management but it also provides the JSON base template deployment to support Infrastructure-as-Code. Which is one of important pillar of DevOps.
-
Azure VNET provisioning using CLI
The Azure CLI 2.0 is Azure’s new command-line experience for managing Azure resources. You can use it in your browser with Azure Cloud Shell, or you can install it on macOS, Linux, and Windows and run it from the command line.
-
Azure SQL provisionig using CLI
The Azure CLI 2.0 is Azure’s new command-line experience for managing Azure resources. You can use it in your browser with Azure Cloud Shell, or you can install it on macOS, Linux, and Windows and run it from the command line.
Learning Azure CLI is pretty simple specially if you are comfort with PowerShell. Following script block shows how to create SQL server with database using Azure CLI
-
Guidance Concerning Petya Ransomware
Would like Share email received from Microsoft today. Hope it will help.
What is the purpose of this alert?
This alert is to provide you with guidance concerning the ransomware issue being discussed broadly in the press starting on Tuesday, June 27, 2017, and causing a large volume of customer inquiries. This ransomware is being described by the press and security researchers as “Petya Ransomware.”
-
PowerShell Desired State Configuration - Part 2
PowerShell Desired State Configuration (DSC)
#DSC Configuration [DSCResource()] Configuration LCMSetUp { param() LocalConfigurationManager { ActionAfterReboot = 'ContinueConfiguration' RebootNodeIfNeeded = $True ConfigurationMode = 'ApplyAndAutoCorrect' ConfigurationModeFrequencyMins = 240 RefreshMode = 'PUSH' } } #Generate MOF File LCMSetUp -Outputpath "c:\DSC\LCMSetUp" #Update LCM Properties Set-DscLocalConfigurationManager -path "c:\DSC\LCMSetUp" -force -verbose #GET DSC Local Configuration Manager Get-DSCLocalConfigurationManager #---------DSC Configuration to Install Windows Feature---------# #DSC Configuration [DSCResource()] Configuration WindowFeatureInstall { param() Node localhost { WindowsFeature IISInstall { Name="Web-Server" Ensure="Present" IncludeAllSubfeature = $true } WindowsFeature SMTP { Name = "SMTP-Server" Ensure = "Present" IncludeAllSubFeature = $true DependsOn = "[WindowsFeature]IISInstall" } LocalConfigurationManager { ActionAfterReboot = 'ContinueConfiguration' RebootNodeIfNeeded = $True } } } #Generate MOF File WindowFeatureInstall -Outputpath "c:\DSC\WFInstall" #Intall Configuration Start-DSCConfiguration -path "c:\DSC\WFInstall" -ComputerName localhost -force -verbose -wait
Please do let me know your thoughts/ suggestions/ question in disqus section.
