Hotfix / Patch build&交货方式 [英] Hotfix / Patch build & delivery approach

问题描述

我们正在调整我们的构建和安装;发布我们的一个基于Java的产品的程序，以支持补丁/修补程序版本。

We are in the process of adapting our build & release procedure of one of our Java based products to support patch / hotfix releases.

今天，我们从构建管道中提供完整的安装包（这是一组包装在ISO中的RPM包）。但是，我们的目标也是支持增量/更细粒度的升级/补丁发货。

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.

为了保持简单作为初始步骤，我们计划拥有更细粒度的RPM包并打包一个子集（仅在发布的范围内更改了）这些RPM在专用修补程序ISO中与完整安装ISO一起使用。 （我们还考虑了其​​他选项，如二进制差异 - 增量RPM - 创建单独的修补程序RPM等。）

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 have also considered other options like binary diff - delta RPMs - creating a separate hotfix RPM etc.)

我想了解如何管理构建管道 - 包装和版本控制（因为这是核心的发布管理问题），以支持这种修补程序部署？

I would like to hear about how you manage your build pipeline - packaging and version control (as this is in the core a release management issue as well) in order to support this kind of hotfix deployments?

推荐答案

我想知道你如何管理你的构建管道 - 包装
和版本控制

I would like to hear about how you manage your build pipeline - packaging and version control

我介绍了一个（工作）概念：

I introduced a (working) concept:

Bugreport作为bug711之类的标识所有来源修复这个bug都会被标记（版本）控制）与错误报告号。

A Bugreport as an identification like bug711 all sources touched to fix this bug will be tagged (Version Control) with the bug report no.

此标记可用于检查创建补丁所需的所有源（如果涉及静态文件，如html，js，css等）并从分支合并到头修订。

This tag can be used to checkout all sources required to create a patch (In cases static files like html,js,css etc. are involved) and to merge from branches into head revision.

在java代码的情况下，部署的最小值是工件（jar，ear，war-file）。
这需要重新启动应用程序。对于JBoss Application Server，我们发现'爆炸'部署允许我们在没有停机的情况下进行修补。

In the case of java code the minimum to deploy would be an artifact (jar,ear,war-file). Which requires a restart of the application. In case of JBoss Application Server we discovered that the 'exploded' deploy allows us to patch without downtimes.

这实际上取决于服务器环境和接近的应用程序类型会最适合你。我担心没有单一的最佳实践。

It really depends on the server environment and the kind of applications which approach would work best for you. I'm afraid that there is no single best-practice.

这篇关于Hotfix / Patch build&交货方式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！