We are heavy users of vNext Release Management. Testing our upgrade of TFS 2017 Update 3 to 2018 Update 1 the artifact trigger, along with each environment's pre-deployment triggers have all been reset.
I can't find anything in the release notes that warns about this. Is there some setting or process we've missed that will avoid us having to re-configure all the settings?
In the below there should be an artifact set, and then lines between UAT, Pre Prod and Prod.
Related
I have been looking for a while now. Is there any way to create something like multipipeline branches from jenkins in TFS 2013?
Multipipeline builds in Jenkins work such that everytime a developer creates a branch in the repository, Jenkins would clone the main build and create a new build specifically for that new branch. Once the branch is deleted, the build also disappears. This way we can make sure that nothing is merged back to master, that did not pass tests or doesn't build.
Is there any way to achieve the same effect in TFS 2013? I know its possible in Azure DevOps but can't find anything specifically on TFS 2013. Sadly TFS2013 is a constraint of the project and cannot be changed.
Is there any way to achieve the same effect in TFS 2013?
I am afraid there is no same workflow in TFS2013, TFS newer versions(e.g. 2015 2017 2018...),Azure Devops Service.
Since TFS2013 is an older version, many features are not supported in this version of TFS.
For example: Triggers, Conditions and so on.
So even a similar workflow cannot be used in TFS2013. I suggest you can update TFS2013 to a newer version, so you will have more applicable functions
In the newer version of TFS, Azure Devops Server or Azure Devops Service, it can use triggers and conditions to trigger build or task to verify the branch.
For example:
You could set CI Trigger for pipeline, and set condition for some tasks. Then when the new branch is created, it will trigger the build. In the build, it will determine the task to run based on the triggered branch（condition).
Or in order to avoid directly merging the branch into the master, you can use PR trigger to pre-merge the branch so that you can verify that the branch is correct.
For more detailed information, you could refer to this doc: Build multiple branches
We have a TFS CI build which builds successfully but the release does not trigger automatically but instead, it triggers after a while. all the settings look correct.
Any suggestions?
I'm trying to find the manual intervention task in the release management of my on Prem- TFS
As per here this is available in TFS 2017. By May it's removed in the latest release?
I searched through the TFS marketplace, but no luck so far.
My TFS Configuration is 16.122.27319.1 (Tfs2018.Update1.RC1)
Could somebody help me to get this task in my release definition?
There are 3 types of phases or ("jobs"):
Agent
Deployment Group
Server (or 'agentless')
Manual intervention goes in a Server/agentless job. You probably have a standard Agent job in your release definition. You'll need to break your release up into multiple jobs: Agent (up to the point where you need a manual intervention), Server (containing the manual intervention), then Agent again.
We are working on TFS 2015 Update 1
The same Job is triggering CI / Gated / Scheduled Build
I want CI/Scheduled build to Publish Artifact
Unable to find a way to disable Build Step Dynamically
I am calling a Powershell Script before 'Publish Build Artifact' Step and trying to find a solution to access the next Step and Set it to 'Skip'
But I have seen even when the Drop folder is empty, the Release (CI/CD) triggers as the Gated Job is creating a Build
Is there a way to avoid Gated Job to create a Build
or to avoid Release Job to trigger in case of Gated Build
In TFS 2015 update 1 I think you're way too far behind. There are solutions for later versions. In your case, you'd need a separate Build Definition for the gated build and if my memory serves me right, you don't have the task group option yet. Task Groups were introduced in TFS 2017, they would at least allow you to share process and variables between separate build definitions.
You're on an unsupported TFS version, in any case, TFS 2015 update 1 was replaced by TFS 2015 update 3.1 any versions between TFS 2015.0 and 2015.3.1 are unsupported and TFS 2015 update 1 contains a number of XSS security vulnerabilities that were fixed in TFS 2015.3.1 as well as in TFS 2017.0.1, 2017.3.1 and 2018.1. This would be a good time to upgrade and make the jump.
In TFS 2018 this would be possible with an artefact tag filter:
Prevent Release Trigger on Gated Check-in build
One option that remains available is to turn off the CI trigger of the release workflow and then from a powershell script, conditionally trigger the release from the build.
Is it possible to trigger personal builds using TFS and Jenkins? Similar to what can be achieved using Teamcity. Can a developer trigger a build without checking-in so that his/her changes can be tested before checkin?
thanks,
You can do this with TFS. Assuming you are using TFS Build, available in TFS 2015 and in VSTS, and your source control is Git, you can setup a build policy for a specific branch that triggers a build any time a pull request happens. Details here.
If you are using the older XAML builds, look at Gated Checkins.