release-management

问题 I'm currently in the process of migrating from full fat on site Release Management to the web based version in TFS 2015. One thing I've noticed is that in the old client you can create a deployment sequence and configure actions to run in parallel, for example I might have these two steps running at the same time: SQLServer - DeployDatabase.ps1 AppServer - DeployWebApp.ps1 In the web based version it appears the equivalent of 'Actions' (now being referred to as 'Tasks') can only be set

问题 I'm trying to set up a token replacement for my config files. I have the source filename set to: $(System.DefaultWorkingDirectory)/TFS Web Build 1.0/Corporate Art\app.RM.config (Here, the RM file is the tokenized config file using token) The destination filename is set to the true name of the config file: Company.Client.Corporate.exe.config I have the json file on the build server at: \0111-03-0555-01\c$\BuildFiles\Transforms.json The transforms.json file has the following data in it: [ {

问题 In short; we want to use a build definition to both generate artifacts for Release Management and checking Pull Requests, but not allow the latter to trigger a new release. We have CI build definition on our Git Repo feeding artifacts into a Release Management Pipeline. Like many teams we also have Pull Requests set up to protect our git master. We'd like to reuse our CI build to validate Pull Requests before they are merged in but doing so automatically triggers our release pipeline

问题 My version of Visual Studio 2013 Release Management Client/Server is Release 4.0. I am using the ReleaseTfvcTemplate.12.xaml template. Is there any way to access the system variables from a release management component (deployer configuration) when using an AGENT based release template? I get NULL when I try to pass $applicationPath or $(applicationPath) or $(ApplicationPath). Here is my status on the deployment of a component in RM that has a custom powershell deployment script: I can

问题 After installing Release Management client and connecting to my Visual Studio Online account I only see 4 actions. Online I see that other people have a lot more actions in their toolbox: 回答1: What you are seeing is correct since in VSO you do pretty much everything in PowerShell using the Deploy Using PS/DSC action. I have a blog post series on Continuous Delivery with VSO here that might be of use in understanding how to get going. 回答2: As Graham pointed out what you are seeing is correct.

问题 I'm installing the Microsoft Deployment Agent 2013 onto an Azure VM. In order to connect to my Release Management Server ( Visual Studio Online in my case ) I need to authenticate either as local system or with a custom account: So with my credentials - I am validated to use the Release Management Service, but I cannot connect with them to the Release Management Server: I, 2015/02/04, 16:50:11.245, User [ME] is system, Admin I, 2015/02/04, 16:50:11.260, Validated account to use as identity

问题 I am new to TFS hence looking for strategies on how people do backup and rollbacks. I would imagine it would go like any other release management system where before new release we backup the old one and keep it easy to re-deploy incase of rollback. My application is a website running on IIS and has SQL databases. Any hints or how you've accomplished it will be helpful. Ideas on the lines of whats Tasks were created, how backups were triggered, and how rollbacks were initiated. 回答1: Once you

问题 I have a need to bulk trigger maven release plugin in jenkins for multiple projects. They are not dependent of each other and some of them have modules. In jenkins you can release each of them one by one, but I'm looking for a method to trigger all at once and potentially label all with same release number. E.g. Project A Project B ... Project N Maven Release (some select query) Next Snapshot version (1.1.0-SNAPSHOT) Next release version (1.0.0) and then project A..N would be released with

问题 I'm developing Release pipeline for our internal LOB applications using TFS 2015 Update2 Release Management. There are various tasks like "Windows Machine File Copy" and "Run PowerShell on Target machines" which needs admin credentials to be passed as input parameters. These admin credentials have Administrative access on target nodes. I'm using Windows service accounts for these. We have an organizational security policy to rotate passwords every year. With that in mind, it is cumbersome to

问题 I'm rather a Git newbie and I'm looking for your advice. In the company I work for we have a "workflow" where we have a single Git repo for our project with 2 branches: master and prod . All devs work on the master branch. If a ticket is done (from the dev perspective), we push to the repo. If all tests are passed, we make a release. The issue is that in most cases, the request from business guys sounds like: "please release ticket A or A && B". In most cases, I end up doing something like