In build definition, I am not able to configure the custom conditions for the tasks in tfs2017 update 1.
This started in tfs2017 update 3. Can you give me an advice to replicate this thing in tfs2017 update 1?
We are planning to configure the custom conditions in build definition. Here, attached custom conditions in tfs 2017 update 3. We want to do this in tfs update 1.
Based on your description, I further checked this problem. Currently, custom conditions are not supported in version TFS2017 update 1. We recommend that you use the version TFS 2017.3 and TFS 2018.
In addition, you can also try to upgrade TFS2017 update 1 to TFS 2018.
Regarding custom conditions, please check the document:
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&viewFallbackFrom=vsts&tabs=yaml#enable-a-custom-condition
Regarding upgrade your deployment, please check the document:
https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started?view=azure-devops-2020
Related
We have a requirement of associating work items with TFS Builds. Generally, this is possible (or we can say 'natural') while using XAML Build Templates in TFS (via Integration Build field of WorkItem. In the below screenshot it was mentioned as 'Integrated In'). We are currently trying to migrate from XAML Build Templates to vNext version of VSTFS 2015 and further to integrate with Octopus Deploy for CI/CD practices.
We are now half the way in the migration because we are stuck up making this vNext templates to associate TFS WorkItems with their Build numbers. Without doing this step, if we complete this migration, it will be difficult to get associated build numbers for each Work Items delivered in that build.
When we searched MSDN blogs, we got a post (link given below) similar to our requirement but I tried that and ended up with no luck.
https://blogs.msdn.microsoft.com/tfssetup/2016/05/09/build-association-with-work-items-in-vnext/
So, please suggest the ways which can resolve our requirement.
Since you are going to migrate from XAML build Templated to vNext. Suggest you also upgrade your TFS version to higher all together.
Just as Daniel point out TFS2015 released already 4 years, kind of little old. Same latest feature in TFS/Azure DevOps are not supported.
What you are looing for is a build-in option in TFS2017 update2 and above version.
Automatic linking from work items to builds
With this new setting in the build definition, you can track the
builds that have incorporated your work without having to search
through a large set of builds manually. Each successful build
associated with the work item automatically appears in the development
section of the work item form.
To enable this feature, toggle the setting under Options in your build definition.
More details refer this blog.
Besides, you could also take a look at our official tutorial Migrate from XAML builds to new builds in case you need.
We have an on-premises TFS instance in our company, and we notice that the sonarqube extension is getting updated automatically. https://github.com/SonarSource/sonar-scanner-vsts
We are worried to have it updated automatically in our production environments, is it really the way it was designed to work? Is there a way to do the updates manually instead or a continuous delivery model?
Yes, this is an expected behavior. In TFS 2017 we added a feature to automatically check for updated external extensions once a day and upgrade them. No way to stop this unless you use a prior version of TFS.
If the account running the TFS Services does not have access to the internet then the jobs will just be marked as failed. They will still attempt to update everyday. To update, you then just have to download the VSIX from the Marketplace and upload it to your local gallery to update the extensions
I'm trying to associate a test run to a release if possible, and if not then a build.
I need to either be able to associate it before the run, or after when we view the history.
I've been looking online and all I can find are references to functionality of 2017 that isn't in 2015.
Is this possible?
It's not possible in TFS2015 for now. You have to upgrade your TFS server to TFS2017updae2. Detail steps please follow this tutorial: Run automated tests from test plans in the Test hub
We are using TFS2017 Update 2, but also there it is, alas, not possible to manually run test cases against a RELEASE.
It is only possible to select a BUILD, which is not accurate in our case, because our RELEASE consists of 5 different SW components, each having it's own BUILD number.
I posted this as a feature request on the user voice forum, here:
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/20579638-add-option-to-assign-a-release-version-to-a-test-r
Please vote.
I need to check version of client's TFS server using my TFS extension.My aim is to identify whether it is TFS 2015.2 (or later version) or TFS 2017. Is this feasible (inbuilt/ out of the box method available) or Is there any workaround available to achieve this. Please help.
As per below post it is possible to differentiate VSTS from TFS. But I need one step forward to get specific version.
How to limit build task only to VSTS not TFS
As far as I know, there is no related rest API will directly return TFS version number.
However as a workaround you could start from one place API-version. For example, the 3.0 API set was introduced with Team Foundation Server 2017. It's not support on TFS 2015.
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