<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/harness">
  <channel>
    <title>Harness</title>
    <link>https://www.linuxjournal.com/tag/harness</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>CI/CD and the New Generation of Software Delivery: an Interview with Harness</title>
  <link>https://www.linuxjournal.com/content/cicd-and-new-generation-software-delivery-interview-harness</link>
  <description>  &lt;div data-history-node-id="1340371" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/harness-logo_0.jpg" width="800" height="400" alt="harness logo" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/petros-koutoupis" lang="" about="https://www.linuxjournal.com/users/petros-koutoupis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Petros Koutoupis&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
Continuous integration and continuous delivery (CI/CD) is all the
rage in the modern world of software development. But actually what
is this pipeline process? It's a method or set of principles for which
development teams implement and deliver code more frequently and reliably.
&lt;/p&gt;

&lt;p&gt;
Continuous integration embodies a coding philosophy and set of practices
propelling teams to implement small and frequent code changes into
version control repositories, while the continuous delivery picks up
where the CI ends and automates the application's delivery
&lt;/p&gt;

&lt;p&gt;
Many platforms, such as Jenkins and CircleCI, exist to help companies and
teams streamline the development and integration of their software stacks,
but not much exists in the way of easing and automating the process
of delivery. And with what &lt;em&gt;does&lt;/em&gt; exist,
the solutions tend to fall short with features and functionality, or they are
overly complicated to configure in the first place.
&lt;/p&gt;

&lt;p&gt;
This is where &lt;a href="http://www.harness.io"&gt;Harness&lt;/a&gt; comes into the picture. Harness produces the
industry's very first Continuous Delivery-as-a-Service platform. Using
machine learning, it simplifies and automates the entire CD process. Steve
Burton, VP of marketing at Harness, recently took the time to
share more details with me.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Petros Koutoupis:&lt;/strong&gt; Please introduce yourself to our readers.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Steve Burton:&lt;/strong&gt; While officially the VP of marketing,
I am a DevOps Evangelist over at Harness. What this means is that
I do a little bit of everything. While most of my career has been in
product management and marketing, I stepped out of the university with
a bachelor's degree in computer science and an initial career in Java
development (ca. 2004 at Sapient), working on large-scale enterprise
J2EE implementations. Prior to Harness, I did geek stuff at AppDynamics,
Moogsoft and Glassdoor. And when not knee-deep in take, I enjoy spending
my time watching F1 and researching cars on the web.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;PK:&lt;/strong&gt; What is Harness?
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;SB:&lt;/strong&gt; We provide Continuous Delivery as-a-Service. It's
the CD bit of the CI/CD equation that helps customers automate how their
software is deployed and delivered to end users in production.
&lt;/p&gt;

&lt;p&gt;
We basically allow customers to move fast without breaking things, so they
can increase developer velocity without the risk of downtime or failure.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;PK:&lt;/strong&gt; What problem or problems does Harness solve?
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;SB:&lt;/strong&gt; Developers are under tremendous pressure to deliver
applications to production, fast and with zero error. It's a constant
pain, one that I personally dealt with as a former Java developer. Our
founders had also seen this challenge firsthand, and that's why they
started Harness.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/cicd-and-new-generation-software-delivery-interview-harness" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 21 Dec 2018 13:15:15 +0000</pubDate>
    <dc:creator>Petros Koutoupis</dc:creator>
    <guid isPermaLink="false">1340371 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
