There is a new Feature in VSTS that allows to chain together related builds:
https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/apr-03-vsts#chain-related-builds-together-using-build-completion-triggers
Is this also available in TFS 2018?
Won't be available until TFS2019 (Azure DevOps Server). See Apr 3rd entry on https://learn.microsoft.com/en-us/azure/devops/release-notes/
Related
I wish to automate management of my Build/Release definitions, for easy backup/restore operations.
How can I do this in TFS 2018? I'm open to using either the REST API or the SDK, although I prefer the SDK whenever possible.
--EDIT--
This is for TFS, not VSTS
In TFS 2018 and later versions, it supports export/import build/release definitions directly. Build/Release definitions are implemented internally as .json files, so you can see details on changes in the file’s history:
Check the following release note:
https://learn.microsoft.com/en-us/visualstudio/releasenotes/tfs2018-relnotes#buildimport
Or you can use TFS REST API to get build and release definitions:
TFS build definition
TFS release definition
Adding a screenshot of how to check build definition history:
I have installed Team Foundation Server 2018 Update 1 and I want to install and configure automated generated builds for the team.
In Team Foundation Management Console, there is an entry "Build and release" but there a only informations and links that are not clickable.
If I click a link, another windows opens, but the ok button stays disabled, so I do not get additional information:
In earlier releases of TFS I could install and configure the tfs build system on this place.
How I can do now in tfs2018. Do I have to install additional software and where I can download.
For one reason, we are using Visual Studio 2015 (we want upgrade later to 2017).
Go to the TFS Web interface, in the settings panel find the Agent Pool and hit the "Download Agent" link.
TFS 2018 is the first TFS version that no longer supports the XAML agent infrastructure.
You need to deploy an agent first as jessehouwing mentiond above, you can also refer to this link for detials : Deploy an agent on Windows
Then create a build definition and Enable continuous integration (CI) to automate builds. Refer to this link for details： https://learn.microsoft.com/en-us/vsts/build-release/actions/ci-cd-part-1
Below articles may also helps for you:
Build and Release in VSTS and TFS
Build and release tasks
Build and release quickstarts
Thanks for the answers. No I have found the page, where I can download the build-agent.
For TFS2018 you can download the build agent by using the following url:
https://{your_server}/DefaultCollection/_admin/_AgentPool
Like provided from Microsoft you can find it for other TFS versions:
VSTS: https://{your_account}.visualstudio.com/_admin/_AgentPool
TFS 2017: https://{your_server}/tfs/DefaultCollection/_admin/_AgentPool
TFS 2015: http://{your_server}:8080/tfs/_admin/_AgentPool
According to the Microsoft documentation we should be able to enable Artifact Filters for Release Environments with onsite TFS 2017 update 3, but this feature seems to be missing from our onsite server.
https://learn.microsoft.com/fr-fr/vsts/build-release/concepts/definitions/release/triggers#env-triggers
Do we need to upgrade to TFS 2018 to have this feature?
The following question discusses the usage of this feature, but not its availability:
VSTS Release Management: filter by branch on artifact source
The documentation isn't clear on this point, and the developercommunity post is incorrect:
https://developercommunity.visualstudio.com/content/problem/175267/release-environment-artifact-triggers-not-availabl.html
The comment below from #MarinaLiu-MSF confirms Environment Artifact Filters feature are not available for onsite TFS 2017 nor for the first release of onsite TFS 2018. To date, this functionality is only currently available in the online VSTS.
I found a post on the VisualStudio User Voice site that mentions it being available in the next major on-prem version: https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/13413054-trigger-release-definition-only-for-specific-branc
ADMIN
VSTS Team (Product group, Microsoft Visual Studio) responded · July 11, 2017
We are happy to let you know that your suggestion is now available on Team Services.
It will become available to the on-prem version in the next major version of TFS.
You can read more about it at https://www.visualstudio.com/en-us/docs/build/concepts/definitions/release/triggers#release-triggers
I am using TFS 2015 as a build server and bitbucket as the source repository. I am trying to implement build trigger on check-in in a specific folder
Like: I have following directory structure in master:
master/driver
master/SRC
I want to have two build configuration for the same branch master ( for driver and other for Product). Each configuration should trigger a build on check in their specific folder.
FYI: Path filters are not available in my TFS 2015
Can set filters on branch only
This feature is not available on TFS2015 update3. You could take a look at below similar question:
git filter in on premise TFS 2015 Update 3
TFS Update 3 missing CI Path Filters
More detail info about path filter you could refer this blog: Path Filters in VSTS Build. To use this feature you should either update TFS to TFS2017 or use visual studio team services.
We would like to host multiple projects in a given git repo and have sub-folder level monitoring for CI. For example:
In a git repo called "Foo", we would like to have following projects:
Foo.Library1 (Would like to publish nuget library called Foo.Library1 with CI)
Foo.Library2 (Would like to publish nuget library called Foo.Library2 with CI)
But when I make a check in code for Library2, I do not want CI for Foo.Library1 to kick in and vice versa.
I was told that this is not possible in TFS 2015, Update 3 (On-premises version).
Can someone confirm or disprove this? If disproving, can you please provide steps on how to go about it?
Yes, there is no way to limit the CI trigger to a specific folder within the repo on TFS 2015 Update3. There is a feature request on the Microsoft UserVoice site and got completed:
Allow GIT CI Builds to monitor changes only in a specific
subdirectory of a Repo
This feature will ship in TFS 15 and is already available on VSTS
https://www.visualstudio.com/en-us/docs/build/news/2016#june-14.
Team Services Group (Product group, Microsoft Visual Studio) responded · August 23, 2016
Then you can do it with path filters on TFS15 and VSTS. Details please refer: GIT filter