release-management

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 ViewDidLoad of both TableViewControllers: if (managedObjectContext == nil) { managedObjectContext = [

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 deployment, we are retaining a large number of builds and the Build Definition's retention policy is

In TFS 2015 we have a build, that will automatically trigger a new release. It is realized with the new script based build definitions . Now I want to pass a user variable from build to release. I have created a variable "Branch" in the build. In the automatically triggered release I try to access it. But it is always empty/not set. I tried it with $(Branch) and $(Build.Branch) . I also tried to create a variable in release with these names, without success. Is there any chance, to access a user variable from the build definition in the release? I do it now with some custom powershell scripts.

I was helped by Sir Athos (thank you greatly) earlier today on a separate question which helped me greatly. I am now stuck at a point where I want to modify a simple text file and include it in my push. So basically I want to add the modified text file to a commit and push it as a commit with it's build number tag as a release. Hope I am making sense here. My code to do try and do this so far is #!/bin/bash YEAR=$(date +"%Y") MONTH=$(date +"%m") git config --global user.email "${GIT_EMAIL}" git config --global user.name "${GIT_NAME}" git config --global push.default simple export GIT_TAG=v2.

I'm looking for some tool (or set of tools) that could help me automate deploying Django projects with all required dependencies. I googled for some solutions but I am curious what are your favorite ones. Arthur Debert I'll second meder's suggestion: user virtualenv + pip. These will give isolated environments that can be mantained and replicated easily. Once you got that running, you have two choices: fabric : Is great for simpler setups. You can script many deploy situations (code checkout, multiple servers, etc). Fabric makes little assumptions on what and how you are deploying, so it's

I'm developing a library for use in other apps and this library has lots of debugging and logging statements thanks to NLog. Is it possible to exclude the reference to NLog.dll when I switch to release mode? Cheers, You can manually edit the csproj file, and do something like this: <Reference Include="NLog" Condition="'$(Configuration)' == 'Debug'" /> This only makes it reference that assembly in Debug. I wouldn't recommend doing this often though, because this behavior isn't reflected in the references list in Visual Studio when you change the configuration. It does work when compiling though