We have just recently upgraded from TFS 2015.2.1 to TFS 2017 and were hoping that we get the possibility to have multiple build definitions as a trigger for a release definition. This feature seems to be available for VSTS (according to https://www.visualstudio.com/en-us/docs/release/author-release-definition/more-release-definition#continuous-deploymentintegration-and-scheduled-triggers) but is still not available in TFS 2017 (see https://www.visualstudio.com/en-us/docs/release/getting-started/release-notes#update-nov16).
Does anyone know why and when this feature will be available in TFS?
According to Feature Timeline this feature was released for VSTS on January 5th; Multiple release triggers with branch and tag filters and will be released with TFS 2017 Update 1; Release management orchestration improvements – branch conditions, multiple artifact triggers.
I've submitted a UserVoice at website below, you can vote it:
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/17687548-add-feature-of-configure-multiple-triggers-for-dif
Related
My team is performing an analysis on which TFS version to upgrade to (from 2010).
One issue that we have faced daily is that TFS 2010 will log pending changes on files that are unchanged. For example, if I edit the JavaScript on HomePage.aspx, while leaving HomePage.aspx.cs and HomePage.aspx.designer.cs unchanged, the later two files will still log as pending changes, resulting with 3 files in the pending changes tab.
This post addresses this issue, and even has a semi-appropriate answer. But I'm wondering, has this issue has been fixed in terms of using TFS 'out of the box' with TFS 2017 or 2018? Do I really need to use TFS Power Tools with the latest version of TFS to get around this annoyance? I see many people saying that Power Tools doesn't solve the issue for all configurations.
That's Visual Studio behavior, not TFVC. I would expect that the behavior will remain the same regardless of the version of TFS you use.
That said, you should upgrade to 2018, period. There's no benefit to upgrading to a version that's already supplanted by a newer major release.
#Daniel is correct. This behavior remains no matter which version of TFS you are using. You could see HomePage.aspx.cs and HomePage.aspx.designer.cs belong to HomePage.aspx, TFS treats them as one file. If you check the history of HomePage.aspx.cs and HomePage.aspx.designer.cs, you'll find no new history produces, as during check-in, TFS detects there is no changes for these two files:
We need to synchronize several projects hosted on Visual Studio Team Services with our on-promise TFS 2015 Update 2. The ultimate goal of TFS is to have CI/CD happening within company for all external projects. However, we don't want to interrupt developers for whom using VSTS will be better choice then TFS.
However, I can't find any solution for TFS to use VSTS as a repository, though TFS can use Git. Maybe, I should look differently on this case. Does anyone know any possible solution?
You'll need tools to migrate between on-premise TFS and VSTS, like:
TFS Integration Tools
OpsHub Visual Studio Online Migration Utility
A useful blog for your reference.
I suspect that setting this up is going to be tricky or it's going to cost you.
The free OpsHub migration utility isn't going to help you in this scenario so you're looking at a commercial product like :
TaskTop Sync or OpsHub Integration Manager
but I haven't used them in this scenario so can't comment on either.
TFS Integration tools would probably do the job but you've got some work to do to get them working and it's not pretty. I have them setup at the minute to sync Work Items from TFS 2015 to VSTS for testing purposes and it works okay. My blog on setting them up with VSTS/2015 is here
Would you not consider doing your CI/CD directly from VSTS rather than an on-premise TFS? You could still have the build/release agent running on-prem and you could lock down permissions for your external devs so you control all the build and releases and any other projects.
Git would be a simpler way of merging code between VSTS and TFS2015 but that assumes you are using Git on your 2015 projects and I believe it would be manual process for someone to do this (someone may be able to comment on a way to make this work)
The new build system is pretty exciting. But...
I would like to know if there's any way to create a build definition with a gated checkin using TFS Version Control like it's available in XAML build definition?
Is it a hidden option or difficult to find? If not, is it possible to develop an extension to do that or must we wait for MS to support it?
Not currently, this is currently scheduled for Q4 2015 for vso and in Update 2 for TFS on prem.
Update 03/02/2016: this has been pushed back to Q1 2016 for vso but still in Update 2 for TFS on prem (which I would assume is also pushed back).
Update 31/03/2016: In Update 2, released 30th March, gated checkin support for TFVC was shipped.
This now shows on the Triggers tab of a build definition:
I noticed that I can change the order of the PBIs of the current sprint on visualstudio.com via Drag&Drop. At work we use TFS 2013 on our own server (I think the newest version Update 4) and that's not possible. Both use the SCRUM template.
Is this a configuration issue? It would help a lot if this would work at our own TFS too. What should I do?
The features available in VSO are beyond that of TFS 2013 update 4. The feature that you are referring to is planned for TFS 2015.
https://www.visualstudio.com/en-gb/news/release-archive-vso
For most customers, regardless of size, I recommend moving to VSO to get access to the latest and greatest features as they become available.
I wish we could use multiple build controllers on the same machine because we have many team project collections but they're not used at the same time so there's no real performance issue here and most of our build servers are not used for extended period of time. I know it's possible to do this with TFS 2010 and TFS 2012 (see following post) but it's an unsupported feature.
Anyone can tell me if it's now officially supported with TFS 2013, I've not been able to find any useful information about this.
This is still an unsupported feature. This feature would be loudly trompetted should it arrive.
On the chances of this arriving in the TFS 2013 updates, I don't expect it. Maybe with TFS v14 (they're skipping v13) or maybe the version after that?
Make your voice heard on UserVoice:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2037679-remove-one-one-binding-between-collection-and-buil
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4417771-use-a-build-controller-over-more-than-one-team-pro
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3872254-tfs-2012-possibility-to-have-more-than-one-build
Update
A new build system was introduced in TFS 2015 and Visual Studio Team Services. It's agent based. doesn't have Controllers and you can install multiple agents on a single machine.
Agents are grouped in Pools and live at the Server level, allowing you to use them across collections.