release-management | 易学教程

How to pass Azure credentials to a Release Management deployment script on a secure manner?

阅读更多关于 How to pass Azure credentials to a Release Management deployment script on a secure manner?

问题 What I want to accomplish: I want to deploy an Azure Cloud Service via Release Management. I managed to get this working by following the steps outlined in this post. In the post the Azure publishsettings file is added to the project and used in Release Management to deploy the Azure package to a Cloud Service. So far so good. What is the issue: The Azure publishsettings file will also contain information about the production environment. I don't want that information to be available to all

“How to get test run id from a specific release using TFS 2018 API”

阅读更多关于 “How to get test run id from a specific release using TFS 2018 API”

问题 We have a task in our release pipeline that runs Seleniumtests(Visual studio test task). The selenium tests run and we can after the run add an attachment to the testrun manually. We also manage to add an attachment with the api but we don't have a good way to extract the testrunid that is necessary for the upload. How do we in a good way get the test run id from a release so we can bind the attachment to the right testrun. We only manage to get all test runs with the api, which is alot.

The account running the TFS build service (NT AUTHORITY\NETWORK SERVICE) needs to be added as a system user in the Release Management Server

阅读更多关于 The account running the TFS build service (NT AUTHORITY\NETWORK SERVICE) needs to be added as a system user in the Release Management Server

问题 I am receiving the above error when attempting to trigger a release from my build. The build works on its own, and the release works on its own, but I cannot trigger the release. My problem is that there is no such thing as a system user in Release Management. There is a Service User, and the above user is set as a Service User. It's also set as a Release Manager. It is also in the Project Collection Administrators group in TFS and has the "Make requests on behalf of others" permission. I've

How to separate between debug and release for connections etc in mvc4

阅读更多关于 How to separate between debug and release for connections etc in mvc4

So I am fairly new MVC4 and many patterns are new to me. However the one thing I am curious about is best practice about release/debug modes. There are a bunch of things for me that differ between live and debug mode and I would like for all of them to be automatic so I don't need to change anything to publish. So for instance I have done like this in my repo (domain project) public class EFAccountRepository : IAccountRepository { private EFDbContext _context; public EFAccountRepository() { #if DEBUG _context = new EFDbContext("name=Debug"); #else _context = new EFDbContext("name=Live");

Why don't I have to release managedObjectContext in the 2nd TableViewController

阅读更多关于 Why don't I have to release managedObjectContext in the 2nd TableViewController

问题 I have two tableview controllers showing CoreData objects. One is a detail view (with sentences) one is an overview (with stories). Pick a Story -> See the Sentences. It looks like I was over-releasing my managedObjectContext; I originally released it in both TableViewControllers in dealloc and got a crash every third time I went between the two controllers (Story -> Sentence -> Story -> Sentence -> Story -> Crash). Some debugging showed I was crashing in my App Delegate after this code in

Error while executing Run Functional Test task in VSTS

阅读更多关于 Error while executing Run Functional Test task in VSTS

In VSTS 2015 we have build and release pipeline setup in a project which is using NUnit test framework. We are trying to configure Integration test case execution using "Run Functional Task" configuration of the task is given in the screenshot below: Visual Test Agent Deployment Task is used to Deploy the NUnit Test Agent in target machine. There is a folder that is created in Target Machine where all test assemblies are getting copied i.e. C:\TestDlls and for NUnit Adapter assemblies C:\PIMPackages The Agent deployment task is getting executed successfully but it get aborted in "Run

The account running the TFS build service (NT AUTHORITY\\NETWORK SERVICE) needs to be added as a system user in the Release Management Server

阅读更多关于 The account running the TFS build service (NT AUTHORITY\\NETWORK SERVICE) needs to be added as a system user in the Release Management Server

I am receiving the above error when attempting to trigger a release from my build. The build works on its own, and the release works on its own, but I cannot trigger the release. My problem is that there is no such thing as a system user in Release Management. There is a Service User, and the above user is set as a Service User. It's also set as a Release Manager. It is also in the Project Collection Administrators group in TFS and has the "Make requests on behalf of others" permission. I've done everything I think I need to do in order to get this to work. The only thing I can think of is

Release Management sets builds to Retain Indefinitely

阅读更多关于 Release Management sets builds to Retain Indefinitely

问题 We are using Microsoft's Release Management tool for automating the deployment of our solution to our various dev servers. This tool is ideal for us because it can perform more complicated deployments that span multiple servers. In this sense, it is working fine and everything is deploying correctly. A minor issue is that after Release Management automatically deploys a build, it sets the build to "Retain Indefinitely" which is indicated by the Lock icon. Since we are doing continuous

What is a good repository layout for releases and projects in Subversion? [closed]

阅读更多关于 What is a good repository layout for releases and projects in Subversion? [closed]

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 4 years ago . We have the standard Subversion trunk/branches/tags layout. We have several branches for medium- and long-term projects, but none so far for a release. This is approaching fast. Should we: Mix release branches and project branches together? Create a releases folder? If so, is

Need primer for a Msbuild newbie [closed]

阅读更多关于 Need primer for a Msbuild newbie [closed]

We maintain a medium sized windows application developed in vb/c# .net in work. Still now the build and deploy process for this app is manual. I am determined to make this process automated using MSBuild on which i have no knowledge still now. Our app has a simple build structure, set of projects already grouped into four solutions(.sln) and just need to build the four slns in an order. And then publish a project(which is part of the last sln to be built) to a directory. That is it. A simple process which is already consuming 30 mins of manual build time and i'm pretty sure that this can be