When using a Docker Registry, like hub.docker.com, you will not often want to delete a published version of an image. You cannot know if someone, somewhere in the world is using that specific version. But when using a repository as part of your CI/CD pipeline, you might have lots of versions that are not used by anyone anymore. So, what if you want to clean the repository automatically? In this article, I will show how the delete images by tag, using PowerShell and the Docker Registry HTTP API V2.

I use the MSTest Parser task in a Bamboo build plan to add a report of tests that were executed and their outcome. But sometimes you want to skip running tests. For example, you are focusing on other changes in your CI/CD pipeline and want to keep the feedback loop as short as possible. The problem is, if you don't run any tests, the parser task will fail. There are no configuration settings to influence this behavior or to disable the task conditionally. I could disable the task manually, but that would affect all other branches at the same time. So, I found it was time to create a quick work around.

The other day I wanted to configure Application Logging on Blob Storage for a Web App Service and found out this needs a SAS URL. And this is something an ARM template can’t provide for you. In this post, I will walk you through the necessary PowerShell code to run.

The other day I needed to get the URLs for all pages in my blog for some PowerShell scripting I wanted to do. Like most websites, this blog has a sitemap and I wanted to use that as a source. As I couldn’t find any existing PowerShell scripts on the web that I could use, I just wrote one myself. Now I like to share this script with you.

My PC just got upgraded to the latest Windows 10 Insiders build (slow ring, build 10565) and suddenly a couple of VMs were missing from the Hyper-V Manager. I first suspected the security settings on the directories were the problem, but my changes didn't fix anything. After browsing around the internet, I found a couple of fixes that might help you if you have the same problem.

I've been running my own mail server at home for years. But it requires a reliable connection and some maintenance once in a while. And of course it always breaks when I'm on the other side of the world. To free myself of that burden I decided to make the move to Office 365. However I discovered there is no way to set my account as a catch-all account. This is not possible at all! So I made my own scripts to add all email addresses I used in the past as an alias on my mailbox.

In a previous post I have written about Using the people picker over a one-way trust. In this post I use STSADM commands as there are no other ways to configure this. A downside of the STSADM command is your domain password being visible on the command prompt in clear text for everybody to read, or to retrieve from the command line history. SharePoint 2010 introduces several cmdlets to replace the “old” STSADM commands. Microsoft has posted an overview of the STSADM to Windows PowerShell mapping. However the commands for configuring the people picker are not available.