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.
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 detached one of our main collections and it failed to detach so we restarted it and everything appeared to be fine. But we found this morning that the Build pipelines are not picking up new builds. The build servers are communicating and showing online but nothing is queuing. Anyone ever experience this during a detach/reattach process?
Update
Customer quiesced and unquiesced TFS and that fixed the pipeline issues.
Detach/reattach collection usually will not effect build related.
First, suggest you to take a look at Event View if there are some useful logs for troubleshooting.
If you are using vNext build, check the agent pool and agents which should all be green.
Make sure in your build definition, you have selected the right agent queue. Also try to create an empty build definition with no build task to see if the issue is related to the definition. And also restart your agent service on your TFS server.
Also check if the service Visual Studio Team Foundation Background Job Agent is running. If not, start it manually and try the build again.
Note: The service is running in TFS server, not build server.
For logs to troubleshooting , check the event view and the log in \agent_diag on build agent to see whether there are some useful information.
If you still get this issue, then deploy and configure a totally new build agent. This will help to narrow down the issue.
We see that when we pause any build definition in TFS2018 and resume, Builds waiting in the queue are all running in parallel.
While this looks good to have multiple builds running parallel, it creates some problems particularly on gated definitions :
creating merge conflicts
Availability of agents for other builds
I could not find much info on internet except one on VS developer community if there is any solution or fix in future TFS update versions
Can someone provide some additional information on this behavior
Environment : TFS 2018 U2 Release environment
TFS Agent version : 2.122.1
We have 1 Team Foundation Server 2017 Update 3 and 3 different build agents configuered. I've noticed that TFS picks the same build agent after when a project have to build. My question is there an option to pick a build agent randomly?
Unfortunately there isn't an option to set that to pick a build agent randomly.
For now, in TFS 2017 it picks the agent in the order that they are registered if the agents are all idle when a build is queued, rather than randomly selecting an agent.
Set Build Agent Priority is an good idea, and there is a user voice here to suggest the feature, you can go and vote it up to achieve it in future.
Currently as a workaround, you can set the demands in build definitions to force building with the specific agents.
To do that, you can reference below articles:
How to send TFS build to a specific agent or server
Build vNext, distributing load to different agents
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.