release-management

问题 I currently have about 16 projects that I build with maven that get deployed to the same application server that make up something like a "portal". I have built a parent pom to handle common dependencies and plugin configurations. Currently, my SVN structure looks similar to this: portal_root +project1 +tags +branches +trunk +project2 . . . +projectn pom.xml The individual projects are each separately deployed. That is, project1 doesn't have a dependency on project2 and each can be modified

问题 I'm using TFS Release Management to do continuous integration and deployment. I'm using migrate.exe to perform the database migration during deployment, and this works great when you're going from an older version to a newer version. When you want to deploy an older version of the application, however, it gets more muddy. Basically, the assembly that holds your migrations for a context must know how to go from say version 3 to version 2. Normally, you use the assemblies you're about to deploy

问题 We have two websites for the same client (main www site and another for the ecommerce site which sits on a seperate server) that use shared portion of code (various features/styles/javascript etc.). We currently manage this by having the shared code as seperate projects (in the same repos) in SVN and using svn:externals to pull the branch of each of these into the two website projects. We have just created two release branches, one each for the two sites. Everything gets commited to trunk for

问题 When I look in the SVN log I really wish I could see markers that tell me when releases were done. I've seen this in other version control systems such as PVCS and Perforce. Can this be done in SVN? I've done a little bit of research and so far it looks like this sort of thing is not supported. Edit We don't want to have to copy our source to a different folder for each release. This results in a huge amount of unnecessary duplication of files on the developers machine and only gives us a

问题 We are using the Release Management, TFS 2013 (previously InRelease) and have a lot of releases that we would like to delete. The problem is that the "Delete" button is always greyed out. What are we missing here? 回答1: This is not possible with the current version (RM 2013 Update 4). Only Releases in Draft state can be deleted. 回答2: The Process of deletion is little complex in the new Microsoft's Release Management 2013. You need to remove all the dependencies for a particular thing that you

问题 When releasing database code to non-development databases , I use such approach - I create release sqlplus script that runs multiple create table/view/sequence/package/etc statements in a sequence. I also should create rollback script which performs drop and other statements if would be needed during deployment or further use. But it is quite annoying always to create rollback scripts manually. I.E. - when I put alter table table_a add column some_column number(5); into release script. I have

问题 I think it's better to release the version of the software which your developers actually tested; I therefore tend to delete the 'debug' target from the project/makefile, so that there's only one version that can be built (and tested, and debugged, and released). For a similar reason, I don't use 'assertions' (see also Are assertions always bad? ...). One person there argued that the reason for a 'debug' version is that it's easier to debug: but, I counter-argued that you may eventually want

问题 I have an MS Access 2016 application that a few people use in one department. I know this whole thing has web dev written all over it but this access database has been their process for a while and there is no time right now to switch over. Recently, a different department wants to use this application, but having their own copy. Currently, if I need to make changes, I'll make the changes in a copy of the app, they send me a current version when I'm ready to import their data, I import it and

问题 Backstory I'm on Rails 2.1 and need to freeze the Capistrano gem to my vendor folder (as my host has broken their cap gem dependencies and I want to make myself as independent as possible). On my local windows machine I've put the following my environment.rb config.gem "capistrano", :version => "2.5.2" config.gem "net-ssh", :lib => "net/ssh", :version => "2.0.4" config.gem "net-scp", :lib => "net/scp", :version => "1.0.1" config.gem "net-sftp", :lib => "net/sftp", :version => "2.0.1" config

问题 I am wondering what is best practice when it comes to dependencies and how releases should be done. In my case I have a library that relies on log4net and I am wondering if I should distribute log4net.dll (set the log4net reference to copy local) along with the release? Could I simply state that log4net should be installed in the GAC? 回答1: Relying on libraries in the GAC can cause version conflicts and other problems that are very hard to troubleshoot and debug. I always try to distribute