Is there any way to get the visual studio build notification tool to work with the new vNext build system?
Currently all I can see are the old xaml workflow based builds available to select for notifications.
I would like to also be able to use this for the vNext scriptable build system.
For VS notification, only XAML build definitions will have notifications. Right now, configure email alert is the only option.
By the way, here is an extensible plugin for TFS named TfsNotificationRelay supports sending notifications to Slack, HipChat and IRC, including notifications for vNext build events, you may take a look at it: https://github.com/kria/TfsNotificationRelay
If you want to see the current build status in tray, you can use Catlight. It supports new vNext builds and Visual Studio Online.
Another option to get vNext notification is use of AnyStatus
Now available as VS extension and will come with desktop app.
Due to a CatLight no longer being free, I've developed a replacement - system tray notifications and a website dashboard for TFS builds (VSTS or on-premises). Early stages but the first version is available here: https://github.com/mattwendels/tfs-build-notifications
Related
I want to implement Team Foundation Server (now known as Azure DevOps Server) for source control and issue tracking. I have only used the on-premises solution previously. For this particular use case, it would be beneficial to have it hosted in the cloud.
I have deployed a VSTS/Azure DevOps Services cloud solution (as opposed to an on-premises TFS/Azure DevOps Server solution), and it seems to have all of the functionality I am used to with the web portal, except there seems to be no direct integration/plugin for Visual Studio.
I can connect Team Explorer to it and query the work items for a basic listing (as shown in the screenshot below) - but if I double click a work item, or if I click New Work Item, it opens in the web browser, not within Visual Studio.
Is this expected behaviour for VSTS/DevOps Services? Do I need an on-premises installation just to get Visual Studio integration or am I missing something? I would like to use their cloud solution as it has a lot of benefits for this particular use-case.
Which opens this:
Instead of this (below screenshot taken from the web):
Any help is much appreciated! I am hoping to get something up and running ASAP, and would rather not have to install & configure a full on-premises solution in the cloud myself. Letting Microsoft handle it is perfect.
It seems odd that there's no Visual Studio support/integration. I have tried on 2 different machines. I have connected one machine which is running Visual Studio 2017 Professional and the other has VS 2019 Professional. Both open and create work items in the web browser instead of within VS. But VSTS/DevOps Services does seem to have all of the other features of TFS/DevOps Server, as far as I can see.
The web portal is great for other stakeholders, but as a developer I like working directly within Visual Studio. In an on-premises installation you get both. Is there any way to do this on a cloud installation?
We need set the Work Items experience in Visual Studio, then we can create new work item in the visual studio.
Steps:
Tools->work items->General->change the option Landing page.
Result:
I am customizing a bug template in Visual Studio Team Services (was TFS Online), and I would like to add a new field called Required Information. but I would like it to be a drop down of the users that I can assign a TFS task to.
So I want a copy of the assign to dropdown.
Can this be done?
It can be done easily in on-premise TFS by modifying the process template. In VS Team Services, although you can customize work items, you cannot modify the process template directly.
Using identity (e.g. a user list) or custom pick-lists are not yet supported. The work to support those features is on-going and is targeted for the first half of 2016, per this blog.
I have a small team working on web site project using Visual Studio 2010 and with Team Foundation server 2012.
In order to have proper control on deployment, I would like to implement my dream deployment strategy as shown in the figure ( https://www.dropbox.com/sc/foy5fh7pntreiha/AAB4L4hhbpjcm1zHi6VBLSa6a )
There is no problem for my team to perform the check in/out between their development pc with the TFS server. But I have problem to deploy code from TFS server to targeted web server.
I read many articles talking about build deploy, but for me I don't think I need to do build because mine is not a web application and we basically have all the codes in the targeted web server. We don't need to build the project into dll and then only upload to web server.
I tried using "copy website" feature in Visual Studio 2010, but on the copy website panel, it is always local programmer pc code at the left hand side and the targeted web server on the right hand side.
I wanted this deployment flow because I think this is the safest flow so that no one will accidentally upload the wrong version of code into the web server. Everyone would have no choice but to check in their code(s) into the TFS server before he/she can upload into the web server.
Please kindly help me.
Thanks
Dont do that.
Instead use Stage / Production server, Stage and Master git branches,
Tell them to exclusively work out of stage, you control the merge to master,
use deployhq or similar service to hook into git(github) and trigger automatic deployments.
Much better than VS, much safer. Should a deploy not work due to file error, DHQ will prevent the entire deployment and revert to old state.
I'm very new to TFS but am using Visual Studio Team Services... which i believe are largely the same configurations and technologies.
Now its possible that VS Team Services only supports web projects but they to be the only type of project that i'm able to build. I've tried several other (non-web) project types including the default console project but I always get a build error similar to one below....
C:\Users\Mark\Documents\Visual Studio 2013\Projects\App1\App1\App.config:
Access to the path 'C:\Users\Mark\Documents\Visual Studio 2013\Projects\App1\App1' is denied.
I'll get a error like the one above for every file in the project.
Can someone confirm whether Visual Studio Team Services does support building other types of projects. If so, is there some special permission or additional setting in build definition that needs to be set prior to triggering build?
Thanks. Turns out all i needed to do was to switch the build template under Build Definition->Process--> Build Process file from default to 'TfvcTemplate.12.xaml'.
Is it possible to publish bug reports directly to Visual Studio Online without having a Visual Studio Online account?
My idea would be that, when a crash of the application happens, the "fail" screen shows an option to send the bug report. I would like this bug report to be automatically added to Visual Studio Online.
I can't seem to find a good up-to-date information about APIs for Visual Studio Online.
I'm also a bit lost about what a "user" of Visual Studio Online is. Is there a way to create "a work-item only user"? In the "standard" TFS those users usually don't need a CAL to access TFS.
If not, it means that all my app testers will use a license for Visual Studio Online, meaning that after the 5 free users, I'll have to pay ~40 USD for someone who will just input bugs/work items?
Each user who needs to login to a Visual Studio Online account will need to have a user plan associated to them (including the free Basic plan allotments) or an MSDN subscription to access the account. We don't have the ability to have anonymous users login to a Visual Studio Online account (or for Team Foundation Server either).
You are right that there is a difference today between Team Foundation Server and Visual Studio Online which allows a "work item only view" on-premises that isn't matched in Visual Studio Online. That access level is called Limited for TFS on-premises instead of Standard. The Standard access level does require a TFS CAL. It's something we are currently exploring now.
Update
Visual Studio Online (and Team Foundation Server Update 4) now allows an unlimited number of stakeholders to have full access to work item tracking for free. This stakeholder license replaces and expands the original Work Item Only View capabilities.
For your testers, the best option for them would actually be Visual Studio Test Professional with MSDN or the new MSDN Platforms offering. This provides them the ability to access Microsoft Test Manager (in the first case) and the web test case management capabilities (in both cases) and allows you to file rich actionable bugs reports.
Update
Visual Studio Online has also been updated to provide the ability to execute test cases as part of the Basic license now. This will be most useful for user acceptance testers who aren't participating in test planning & test authoring but have been assigned a set of test cases to execute.
For your question about up-to-date API information for Visual Studio Online - it is the same documentation as the the TFS SDK at the moment. You can use the TFS SDK to build extensions for both Team Foundation Server and Visual Studio Online.