Channels ▼
RSS

.NET

OpenMake Heralds DevOps Maturity


OpenMake Release Engineer arrives this month, promising to centralize the management, configuration, and reuse of all Release and Deploy elements for the enterprise software developers.

Its development team points out its design functionality that allows Operations to define release standards that can be inherited and customized specifically for each project team. It supports multi-tiered platforms with "no reliance" on any agent technology.

"Release Engineer leverages a Domain Model to support object reuse that facilitates the sharing of release components and dependencies for use across teams and delivers a unique roll forward logic for incremental release processing at both the application and database levels," said the company.

Release Engineer is positioned as a product capable of allowing teams to reach what the company calls higher levels of "DevOps Maturity" by eliminating the errors and bottlenecks found in one-off deploy scripts. Instead, it provides a "reusable and auditable" model-driven framework is used for designing, planning, and shared control of the entire release and deploy requirements.

Release Engineer is supposed to enable less risky releases and deployments with greater efficiency due to automation and abstraction. It enables incremental deployments using its "Roll Forward" approach to determine which component versions of an application require updating. This minimizes the need for performing monolithic deployments and instead supports Agile, continuous deployments where changes are moved forward on a frequent basis.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video