java - Hotfix / Patch build & delivery approach -


We are in the process of building and optimizing ours; The release process of one of our Java-based products to support patches / hotfix release

Today, we have a complete installation package (which is a set of RPM packages wrapped in an ISO) Pushes out of the pipeline. However, our goal is to support incremental / more subtle upgradation / patch shipments.

In order to keep things as simple as an initial step, we plan to prepare RPM packages for a maximum and a dedicated hotfix is ​​converted into a subset of these RPMs (only in the realm of release in ISO ) Plan the package with full installation ISO (we have considered other options like binary inter-delta RPM - a different hotfix RPM etc.).

That not it would like to hear how you manage your build pipeline - packaging and version control (as it is also a release management issues core to support such hotfix deployments)?

I would like to hear about the management of my build pipeline - packaging and version control

I introduced a (work) concept:

A bugreport as an identity such as bug711 to fix this bug, all the sources touched in the bug report number Will be tagged with (version control)

To tag all tags needed to make this tag patch, check Can be Emal is (are involved static html, js, css etc. files) and to modify the head of branches.

In the case of Java code, the minimum deployment will be an artwork (jar, ears, war file). For which the restart of the application is required. In the case of the application server, we found that 'Explosion' deployment allows us to patches without downtime.

It really depends on the server environment and such applications that work best for you, I fear that there is no best practice.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -