What is Azure DevOps and why aren't you using it?

-

 I wanted to answer what the "Azure Devops" Microsoft suite is as many people may not understand the powerful tool that it is and as a former consultant I see a lot of people have a ton of disparate tools when Microsoft makes it easy. 

So - here are 5 reasons to use Azure Devops.

1) Replace JIRA

Azure Boards can replace your backlog in JIRA. If you run an agile team, you probably use Jira - however you can easily use Azure Boards and replace your JIRA backlog. The benefits are that you are buying into the Azure DevOps suite and have one tool to manage your code and backlog. JIRA can be expensive, so it makes sense to start a new project with Azure Boards - no need to default to JIRA.

2) Replace Bitbucket, Gitlab, TFS, etc.

Azure Repos enables users to write to private cloud hosted repos. This way you can not only take advantage of having a Microsoft hosted and private repo, but you can easily integrate with the other tools in the Azure Devops suite like Test Plans & Pipelines.

3) Replace your testing tools like Zephyr.

A tool like Zephyr allows you to integrate tests into your SDLC pipelines, however Azure Test Plans can replace this functionality and easily allow tests as part of your SDLC process.

4) Replace tools like Artifactory

As an Azure Devops engineer you can retire tools like artifactory and instead use the public and private Azure Artifacts to enable package management solutions like npm, and pip server to host your system artifacts.

5) Replace your Jenkins pipelines

Finally, you can get rid of having Jenkins and use Azure Pipelines to run CI/CD. This enables the single plane of glass and allows you to run your code, your tests, and your deployments in the same workflow. 


Buying into this eco-system enables you to have a single pane of glass view of your entire software development lifecycle for a ridiculous value.

Comments

Post a Comment

Popular posts from this blog

Azure - Check Invitation Status to guest user

-
Image
Often times you will need to invite a 3rd party to your Azure AD tenant to support your environment. When you add them to a resource, they will automatically be invited as a guest user in your Azure AD tenant, however they won't be able to access this until they accept the invitation email. If you send an invite to a guest user you can see if they have accepted the invitation or not. You also have the option to resend the invitation. From Azure AD you can search for guest users and drill down into an individual one. Here is what the email looks like - the key here is the email comes from " [email protected] " because it can be sent on behalf of this may end up in the junk or spam email folder, so be sure to have them check there.
Read more

Blogs for Azure Information

-
Here are some of the blogs that I follow for information around new features in Azure, OMS, Log Analytics, Azure Monitor, etc. Azure Monitoring Services Health Status https://blogs.msdn.microsoft.com/servicemap-status/ Microsoft Azure Roadmap https://azure.microsoft.com/en-us/roadmap/ System Center Me http://systemcenterme.com/ Quae Nocent Docent (Great weekly OMS, SCOM, and Azure Info) https://nocentdocent.wordpress.com/ Operations Management Suite Blog https://blogs.technet.microsoft.com/msoms/
Read more

Azure Point to Site VPN failure with error code 809

-
I ran into some trouble today troubleshooting a developer's workstation. The issue was when using a Point to Site IKEV2 VPN some clients could not connect - they received an error: The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem. (Error 809) The strange thing was that some other workstations seemed fine. After bashing our collective heads against the wall, checking checking the P2SChild, doing all sorts of network troubleshooting to the endpoint DNS name -  azuregateway-8fc2c9e3-26cd-432a-ae47-92b7f6422a5d-e1a7e8cec41d.vpn.azure.com , editing registry, checking firewalls, etc, we finally determined the caus
Read more