With a good foundation of the basic to work from. We now can go deeper into DSC authoring phases. The authoring phase is the first part of a two-part phase. The Pull and Push modes is the second phase that deserves a blog post on its own.
In the last post, we talked about PowerShell and DSC at a technical level. In this blog post, I wanted to cover the challenges and bottlenecks that I see within companies as the code enters the build, test and release process (BTR process). To be clear, I am not talking about the practices of how to perform build, test and release. What I am referring to is configuration drift, which is the change from a baseline to a new configuration state. Continue reading
In today’s PowerShell Powerbit, we are going to look at the Desired State Configuration (DSC) foundational technologies in more detail. When learning anything new, like PowerShell or DSC, defining and understanding the foundational technologies and acronyms are essential. Continue reading
In the last Powerbits post, I talked about the basics of PowerShell and how it’s the foundational building block for DSC. In this post we will be covering the required installations for DSC and how to connect to Azure. Continue reading
With all the latest Microsoft releases it’s apparent that PowerShell and Desire State Configuration (DSC) is at the core of build, releases, and configuration management. If you have not learned PowerShell, now is the time to get on board. DSC is a recent practice that was released in early 2013. The DSC uses PowerShell’s core features as its foundational building blocks. Continue reading
At the heart of any continuous delivery practices is automation. If you still heavy manual process in you delivery process. Well to be frank, you are doing it wrong! There is no other way to say it.
There is no gray area when it comes to automation and continuous delivery (CD). Automation is at the core of continuous delivery
I recently had a customer that asked “How can I tell if the proxy server would be a benefit to my offshore team”. This is a good questions that needs data to compare the before and after proxy.
The first question is how to get the data. You can run a get of a project in source control on a workstation at the remote location and capture some general times. A better method is to use the “_oi/_diagnostics/activityLog” log that is available.
The build and release process is the backbone infrastructure of software development. While it may not be the coolest or hottest part of the software development process, it is a very necessary one.
Why, you might ask?
Software delivery is about reduction of risk and waste, ROI on new features, and flow of value to our customers. Yes, we have heard these definitions before, but how do these definitions really relate to our everyday lives? Continue reading
We have all seen the latest buzzwords of Continuous Delivery over the last few years. The name “Continuous Delivery” gives a general idea of the practice: continuously deploying an application or code into a system. The word “continuous” does not provide the detail of what we are trying to achieve in the Continuous Delivery practices. This is where the 3R’s of Continuous Delivery come in: Reliable, Repeatable and Reusable. Continue reading
Before I do an upgrade I always ask for the size of the TFS database set. It provides me the information on how long an upgrade might take. The queries below, also provides information of attachments that might be taking up extra disk space. By reducing the overall database set, the whole upgrade process will go faster. Plus, it is a good time to do some house cleaning.