release-management

Hotfix / Patch build & delivery approach

左心房为你撑大大i 提交于 2019-12-05 09:45:18
We are in the process of adapting our build & release procedure of one of our Java based products to support patch / hotfix releases. Today, we deliver a full installation package (which is a set of RPM packages wrapped in an ISO) out of our build pipeline. However, we aim to also support incremental / more fine grained upgrade / patch shipments as well. To keep things simple as an initial step, we plan to have more fine-grained RPM packages and package a subset (only the changed ones in the scope of a release) of these RPMs in a dedicated hotfix ISO along with the full installation ISO. (We

Versioning and release management with multiple products with shared code base

六眼飞鱼酱① 提交于 2019-12-05 08:56:12
I am currently trying to figure out, how to do release management with git flow in a scenario where I have one git repository with about 15 projects in two solutions plus scripts for the database. Each solution basically contains one project that will result in an executable and more than 10 projects containing base functionality used by both solutions like DAL, SAP access wrapper etc. Solution one is an application with UI for the users. Solution two is a Windows service. The release of the two solutions and the database are not in sync. This means that frequently only one ore two of the

Problems using git diff to create file list for deploy

时光毁灭记忆、已成空白 提交于 2019-12-05 05:08:35
问题 I want to use something like the following command to create a tarball to deploy: tar cjvf ~/deploy.tar.bz2 `git diff --name-only 0abc 1def` The inner git diff command produces a list of files with relative including the relative path when i run it separately. I'm running into two problems though, I need to be able to auto escape spaces in the output, so tar doesn't complain about files containing spaces and when the tar does get created, all the files have a duplicate 'hidden file' preceded

VSTS Release - Define custom variable in web.config and set at release time

落爺英雄遲暮 提交于 2019-12-05 04:52:52
I am trying to replace an appSetting at release time using VSTS Release. All post on the web refer to the old release management tool or refer to the new one but mention the replace tokens task. This task does not exist so I presume it is built in. I have set up my web.config ( MyVar ) and set up my environment variables but nothing gets replaced. And here is my release: I apologise if I am being stupid but I just can't work this out, mostly due to out of date documentation. Update 2: Ok so after some help from a couple of people I am now on the right track with this. I have added the Colin's

Is it possible to create a docker container from TFS and deploy a release build to it?

江枫思渺然 提交于 2019-12-05 02:46:34
We are running on-premises TFS 2017. I would like to create a release definition for our QA team which will create a Docker container running Windows 7, and deploy our release build to it automatically. Once the deployment is done the QA team should be able to log onto the container to test the app. No manual running of a MSI installer or Setup.exe. Ideally each queued release will create its own container with its own copy of the released build. Is this possible? Or recommended? All our servers and hosts will be in-house, we will not be using Azure. Thanks in advance for any advice. It is

What are the options for release management using Jenkins

微笑、不失礼 提交于 2019-12-05 01:15:55
问题 I'm evaluating build engines like Jenkins and Apache Continuum. The bulk of our build is using Maven. What options are there in Jenkins for release management? By release management I mean the process of creating a release from a branch in source control, then updating the version tag in Maven. For example, if my Maven project (parent + child sub-projects) is currently at version 5.5-SNAPSHOT, I would like to tell Jenkins to check out, build, and test the latest of this branch, and update the

Getting TravisCI to commit and push a modified file with Tags (releases)

自古美人都是妖i 提交于 2019-12-05 01:14:36
问题 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}"

Django deployment tools

孤街浪徒 提交于 2019-12-04 19:43:20
问题 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. 回答1: 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

Visual Studio - How to remove a reference in Release mode

南笙酒味 提交于 2019-12-04 16:52:47
问题 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, 回答1: 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

GNU make with many target directories

南楼画角 提交于 2019-12-04 13:47:53
问题 I have to integrate the generation of many HTML files in an existing Makefile . The problem is that the HTML files need to reside in many different directories. My idea is to write an implicit rule that converts the source file (*.st) to the corresponding html file %.html: %.st $(HPC) -o $@ $< and a rule that depends on all html files all: $(html) If the HTML file is not in the builddir make doesn't find the implicit rule: *** No rule to make target . If I change the implicit rule like so $