Let’s go over the Package Management functionality in Visual Studio Team Services (VSTS) and how we can use Service Hooks.
Service hooks allow you to integrate with other products and services. They are available under the Gear icon > Service Hooks. If you click add you will notice you can integrate with many different services.
Example: Notifications of new Bugs
When my stakeholders started do testing I realized bugs could be coming in and I wouldn’t be aware of it. I didn’t want emails - I wanted push notifications sent to my phone. I accomplished this using Slack and a Service hook.
- I did was setup a new Slack team, just for myself. Eventually I could invite my stakeholders
- Note that VSTS has a “Team room” for chatting but its being phased out
- I setup the team on my phone
- Within the Slack team I created a channel called Bugs
- In the bug channel I set it to send me push notifications for Any kind of activity
- Clicked the Gear icon > Service Hooks
- Clicked the green + icon to add
- Selected Slack from the list
- Clicked Next
- For the Trigger on this this of event I selected Work item created
- For Work item type I selected Bug
- Clicked Next, entered the Webhook URL from Slack
- Clicked Test, to confirm it worked
- Clicked Finish
[caption id="attachment_2430” align="alignnone” width="1076”] My slack channel with my test bug. Note that I set the Notification Preferences > Mobile push notifications to Activity of any kid[/caption]
Suppose you want to create a NuGet or npm package for internal use. You can use something my MyGet but it’s yet another product/service.
As I write this, the package management service is relatively new and it’s free for up to 5 basic users. That’s great for us!
Installing the Package Management functionality
Technically this is an extension which you must install. It doesn’t come with VSTS by default.
Once you’ve set it up you will see a new menu option under Build & Release > Packages
So… how do I use it?
Once it’s setup you will have a feed URL. You can manually publish packages or get the VSTS build system to do it for you.
If you have a NuGet package you can setup Visual Studio to point to the URL.
More info on Package Management in VSTS
As a lone wolf, I’m not sure how much use this will be. I’ve only ever created one NuGet package. If you’d like more information check out this page.
I hope this series of blog posts has helped.
Many of the people I’ve spoken to have no idea what VSTS can offer them. They view it as something big, scary and expensive. But worse of all: some people instantly dismiss it the moment they see it’s from Microsoft. I’ve been using VSTS since the day it came out and have enjoyed using it and watching it improve over time.
Congrats on reading this far! You have unlocked the “white wolf” achievement for reading the whole blog series!
Previous: Builds and Releases