release-management

问题 I have a few open source projects that I manage. I've been posting the .tar.gz releases for them to a directory on a webserver I run. I would like to post them to github. Is there a simple way to post the release and a signature for the release? My users aren't sophisticated enough to download the release with git; they want to download and install a .tar.gz file. Some of them may even want to verify the signature. 回答1: GitHub have just announced their new "GitHub Releases" feature, which

问题 I read somewhere (sorry don't exactly remember the source) that facebook has release Tuesdays. They release the new features to their internal employees first, then to a small set of external users and then to the whole world. I believe google also does something similar I work primarily with Microsoft stack (TFS for source control, IIS, asp.net, sql server with huge data). Public facing sites of course, so they have to be up 24x7x365. Though I can envision releasing my api/dll only on one of

问题 UPDATE: example repository, https://github.com/so-gitdemo/so-gitdemorepo In the context of the github repo. How can I easily locate rev "b0430cee"? I know I can just look, but the real example that this repository mimics has a dozen committers and multiple other branches. Not quite as easy to use inspection. How can I find the branch creation revision when the branch has been merged multiple times? I am aware of this question: How to determine when a Git branch was created? The solution does

问题 In TFS 2017 Update 1 after downloading programmatically a release definition with REST api, I edited the downloaded json and uploaded again programmatically. The changes are present. However the server phase of manual intervention is missing in the environments after the changes. Can someone else reproduce it? The program C# to download and upload the release definition is at my github page githubpage 回答1: Use api-version=3.2-preview.3 instead of 3.0-preview.2 when you update the release

问题 Using agent-based release templates, not vNext, how do I configure a "Create Folder" item so that it incorporates the date into the folder name, e.g. "C:\inetpub\wwwroot\backups\MyApp\02-03-2015\". Preferably, I would like the build number instead of the date but I believe it's only available to vNext templates. -edit- unless you're using components I'm trying to implement some backup and rollback logic as part of the my release pipeline. I want to copy the existing web code to a backup

问题 Using agent-based release templates, not vNext, how do I configure a "Create Folder" item so that it incorporates the date into the folder name, e.g. "C:\inetpub\wwwroot\backups\MyApp\02-03-2015\". Preferably, I would like the build number instead of the date but I believe it's only available to vNext templates. -edit- unless you're using components I'm trying to implement some backup and rollback logic as part of the my release pipeline. I want to copy the existing web code to a backup

问题 I am creating a django-based site that will serve flash apps that occasionally access data via pyamf. I need to be able to easily test the flash in the context of the django framework, i.e. with all the login cookies and everything available, so that when I make a pyamf call, it has all the user context there. And I need to be able to test and release both the swf's and the wrapper html's in a sane way. However: The html templates in flex are already templates, so if I put template code in

问题 In TFS 2017 Update 1 (On-Prem) there is a release definition with a manual intervention step in between. The manual intervention notification is set for a group where an user User1 is not part of. User1 has Builder and Project Admin rights; And is also part of the TFS team. During the manual intervention of a release User1 is able to resume or reject the release. But we don't want this to happen. I could not find the rights in TFS Microsoft online documentation for being able to do this. What

问题 I'm trying to connect a Deployment Agent to my Release Management server with TFS (all running Update 2). The Release Management server is outside the network of the test environment servers. It can be reached over HTTP. The test environment is running behind a proxy. I've changed the configuration of the config files to make sure connecting through the proxy works by adding this: <system.net> <defaultProxy enabled="true" useDefaultCredentials="true"> <proxy usesystemdefault="True"

问题 I am using Release Manager 2015 to deploy my application. I am using Microsoft's Extension Utilities pack to do this: Extension Utility Pack - Documentation This simply states: Tokenization based pattern replacement This task finds the pattern __<pattern>__ and replaces the same with the value from the variable with name <pattern>. Eg. If you have a variable defined as foo with value bar, on running this task on a file that contains __foo__ will be changed to bar. So in my web.config.token