Trigger a Release add the Build to GlobalList

This was never the best solution but it worked. When a build executed it would be added to the Collections Global List. Then it could be used as the source for drop downs like Found In Build and Integrated In Build.

If you are stuck in that place between TFS 2015 U1 and U2 you have the news builds but you don't have the new Release manager yet these two PowerShell Scripts might come in Handy.

There are so many environment variables you can use to get information about the build that you are a part of, the CollectionURI, SourcesDirectory and so on. You can check them all out here.

To save space I have left out error checking.

  1. Trigger a release in ReleaseManager from the 2015 vNext build

# Environment Variables

Write-Host "URI: $env:SYSTEM_TEAMFOUNDATIONCOLLECTIONURI"

Write-Host "Project: $env:SYSTEM_TEAMPROJECT"

Write-Host "Build Def: $env:BUILD_DEFINITIONNAME"

Write-Host "Build Number: $env:BUILD_BUILDNUMBER"

 

[string] $TFSUri = $env:SYSTEM_TEAMFOUNDATIONCOLLECTIONURI

$TFSUri = $TFSUri.Replace("/tfs/",":8080/tfs/")

write-host "URI - $TFSUri"

 

$binaryLocation = join-path (Get-ItemProperty $registrykey[0]).InstallDir "bin\ReleaseManagementBuild.exe"

 

# Call Release Management Build

&"$binaryLocation" release -tfs "$TFSUri" -tp "$($env:SYSTEM_TEAMPROJECT)" -bd "$($env:BUILD_DEFINITIONNAME)" -bn "$($env:BUILD_BUILDNUMBER)"

 

 

  1. Add the Build to the GlobalList

#Use Environment Variables to get Build Information

[String] $GlobalEntryValue = "$env:BUILD_DEFINITIONNAME/$env:BUILD_BUILDNUMBER"

 

#Some other information that you will need

[string] $GlobalListFileName = "GlobalList.xml"

[String] $GlobalListName = "Builds - MyProject"

[string] $tfsServer = $env:SYSTEM_TEAMFOUNDATIONCOLLECTIONURI

[string] $witadmin = "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\witadmin.exe"

 

#Export GlobalList

$arguments = 'exportGloballist /collection:"' + $tfsServer + '" /f:"' + $GlobalListFileName + '"'

write-host $witadmin $arguments

start-process -FilePath $witadmin -Argumentlist $arguments -wait -WindowStyle Hidden

 

 

#Add the Entry to the Global List

Write-host "Add build $env:BUILD_BUILDNUMBER to $GlobalListName"

[xml]$doc = Get-Content($GlobalListFileName)

$List = $doc.GLOBALLISTS.GLOBALLIST | ? { $_.Name -eq $GlobalListName }

$build = $doc.CreateElement("LISTITEM")

$build.SetAttribute('value',"$env:BUILD_DEFINITIONNAME/$env:BUILD_BUILDNUMBER")

$List.AppendChild($build)

$doc.Save($GlobalListFileName)

 

 

#Import GlobalList

$arguments = 'importgloballist /collection:"' + $tfsServer + '" /f:"' + $GlobalListFileName + '"'

write-host $witadmin $arguments

start-process -FilePath $witadmin -Argumentlist $arguments -wait -WindowStyle Hidden

 

Microsoft Events

TechNet Virtual Summit

3 days of expert content on IT shifts, career insights, security, mobility, tech innovations and more. Hear firsthand where IT is heading, from some of the best tech minds in the business. Join us online March 1-3 right from your favorite connected device. Register here: http://aka.ms/tnvcmvp and share with your community! Note:  sessions will be delivered in PST Time.

Let's Dev This Tour in Montreal

On March 30st, Let's Dev This Tour is coming to Montreal to present 3 different tracks on Web, Cloud and Windows 10. To know more about each session simply click on it.

Microsoft DevOps Hackathon

DevOps Hackathon is happening in Montreal on March 18-19th and in Ottawa on March 31st- April 1stPlease see below call for MVP Proctors.

MVP Open Day 2016 – this year's Canadian MVP Open Day will take place on Friday, May 6th, 2016 (8:30am – 5pm EST). Please make sure you register here

ITI Cloud Roadshows: Join local IT professionals and Microsoft MVPs in the following cities:

MVP Days Community Roadshow: coming to Toronto Feb 29th, Ottawa Mar 2nd, and Montreal Mar 4th, 2016. We are hoping you are able to register for these events. Please help us spread the word.

SharePoint Saturday Montreal: Register for the 4th Edition of SharePoint Saturday in Montreal on April 2, 2016. Five tracks offered: IT Pro, Dev, End-User, Business Customer Showcase and Data SQL. Call for Speakers and Sponsors are open!

Prairie Dev Conference: 2-days Development Conference happening in Winnipeg on April 11-12th, 2016 - http://www.prairiedevcon.com/

MVP Community RoadShow

There's just one week left for MVPDays Community Roadshow in Toronto!

We would love to see you there!

Please use the Promo Code "CDNMVP" to register for FREE !

 

Make Web Not War

 

Make Web Not War brings together Canadian web dev experts to talk about modern web standards, Open Source, and Open Data innovations. Learn about the latest IETF & ECMA web standards, how to run and contribute to open source projects, the importance of open data in the world of journalism, open government, and more. Live online Feb 5, 2016. Participation is free. Register to receive exclusive content to accompany the live presentation.

 

URL: https://aka.ms/mwmvp

LET’S DEV THIS!

#LetsDevThisToronto

 

Awesome apps are built a certain way – that way may be different for each and every one of us. On February 10, Microsoft DX is coming to Toronto with Let's Dev this Tour to help you learn how to build awesome apps for web, cloud and Windows 10 using latest standards and tools. The day will be full of great workshops, hands-on-labs and consultations with experts.

 

1 DAY. 1 VENUE. 3 DEEP DIVE WORKSHOPS – WEB. CLOUD. WINDOWS 10.

 

Pick a primary workshop, then pop in and out of all three based on the topics that interest you the most.

 

 

 

WEB

The boundless web

Build across browsers, devices, and the cloud.      

Sessions and hands-on labs on the latest dev standards and tools‚ Web Apps with Node.JS‚ and Azure.   

 

 

 

 

CLOUD

The fusion of apps and the Cloud

Magic happens when the technologies that you love live on Azure.

Sessions and hands-on labs on App and Data Services‚ VMs, and networks.

 

 

 

WINDOWS 10

One app fits all

One app can fit them all
– mobile, tablet, and PC
– with Windows 10.

Sessions and hands-on labs on Adaptive UX‚ the Universal Windows Platform‚ speech recognition, data binding‚ and Azure.

 

SPACE IS LIMITED per workshop so please reserve you seat now.

Excluding weekends in Azure Automation Runbooks

Getting Azure Automation runbooks to shut down your virtual machines (or turn them on) automatically is not new. There are a lot of scripts out there that could do it for you. You can also write one yourself. It's not that complicated. I did it J Just kidding…

There are a couple of ways my PowerShell scripts are different:

  1. First, the scripts that automatically start/stop Azure virtual machines take the weekend into account. Scripts will not turn your machines on or off on the weekends. After all, you probably do not want to automatically turn on your virtual machines in Azure early in the morning on the weekend, just so that you can turn them off at the end of the day on the weekend. Seems like a waste, right? Anyways, this small change should save you a few bucks.
  2. Second, the scripts adjust the schedule from UTC to the time zone you need. It looks like when the scripts that are part of Azure Automation runbooks run, they use UTC time. So, if you're in Toronto, script will think that the weekend starts 5 hours earlier. It's not bad, I guess. But, it also means that the weekend will end 5 hours earlier, and that just not right and need to be fixed.

Below is a code snippet that makes the above mentioned happen:

$UTCTime = (Get-Date).ToUniversalTime()

$TZ = [System.TimeZoneInfo]::FindSystemTimeZoneById("Eastern Standard Time")

$LocalTime = [System.TimeZoneInfo]::ConvertTimeFromUtc($UTCTime, $TZ)

$day = $LocalTime.DayOfWeek

if ($day -eq 'Saturday' -or $day -eq 'Sunday')

{

Write-Output ("It is " + $day + ". Cannot use a runbook to start VMs on a weekend.")

Exit

}

 

The complete scripts that start or stop Azure virtual machines can be downloaded from OneDrive. Enjoy.

Accessing Git from Behind the Proxy

So, you have installed Git client and trying to connect to Git server (on Visual Studio Team Services, Github, or whatever), but you're getting "fatal: unable to connect a socket (Invalid argument)" error. One of the reasons could is that you're behind the proxy. For example, you're at work and your employer requires all internet traffic to go through the proxy. ~/.gitconfig global config file is the key here. In this case, to get Git client to work with the proxy, you need to configure http.proxy key in git config using one of the following commands:

git config --global http.proxy http://proxyuser:proxypwd@proxy.server.com:8080

or

git config --global https.proxy https://proxyuser:proxypwd@proxy.server.com:8080

  • change proxyuser to your proxy user
  • change proxypwd to your proxy password
  • change proxy.server.com to the URL of your proxy server.
  • change 8080 to the proxy port configured on your proxy server

If you do not need to authenticate to proxy, then just specify proxy server name and port number and skip proxy user and password.

 

If you decide at any time to reset this proxy and work without (no proxy), use one of the the following commands:

git config --global --unset http.proxy

or

git config --global --unset https.proxy

 

Finally, to check the currently set proxy, use one of the following commands:

git config --global --get http.proxy

or

git config --global --get https.proxy

 

By the way, to retrieve the proxy settings you're using, you can use one of the following commands:

reg query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver"

or

netsh winhttp show proxy

That's all I got to say about Git and proxy server.

TFS-GIT Release Notes

I was recently having trouble generating some Release Notes for a current project that is using Visual Studio Online Visual Studio Team Services.  With Git as our backing source control system there didn’t seem to be an easy way to see what Work Items were going into a release.  Thankfully we are associating Work Items with commits which makes the following Powershell script work. 

Passing in our current release branch, and our previous release branch we can isolate the new commits and then parse their commit messages looking for the “Related Work Items:” text that Visual Studio appends to commits.  Once we have those WorkItem ids we can use the TFS api to get some info about them and create some release notes.

 

You can find the script on GitHub.

MVPDays Community Roadshow 2016

MVPDays is a series of one day events that focuses on content for IT and Dev Professionals sharing their knowledge allowing local communities to learn more and advance their skills based on real world experiences.  The majority of the sessions are Content will focus on the following topics: 

  • Cloud
  • IT PRO
  • SharePoint / Office 365
  • Development

   

It will be held in the following cities:

 

More great resources from Microsoft

 

Announcing the Microsoft Cloud Roadshow

This is a free, two day technical training event for IT Professionals and Developers that provides best practices and insight from those who run cloud services across Office 365, Micros oft Azure, and Windows 10.

Developer Interview Series #1 -

In this interview series, we bring you best practices, anecdotes, and insights from developers who are building creative solutions using Microsoft technologies.

The Power of Cross Platform Development with Universal Apps and Xamarin

We're on the road to self-driving business applications

A blog by Steve "Guggs" Guggenheimer on self-driving ERP (Enterprise Resource Planning software)

Memory Compression in Windows 10 RTM

The OS is doing some clever optimizations that allow your processes to trim some of the memory but not necessarily page it out to disk.

Managing hidden apps, beta apps and visibility of in-app purchases in Dev Center

The unified Dev Center introduced several new options to manage the visibility of apps and in-app purchase.