<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cicd on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/cicd/</link>
    <description>Recent content in Cicd on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Jan 2019 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/cicd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure CI/CD Pipelines @Troopers ’19</title>
      <link>https://insinuator.net/2019/01/secure-ci/cd-pipelines-@troopers-19/</link>
      <pubDate>Thu, 10 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/secure-ci/cd-pipelines-@troopers-19/</guid>
      <description>&lt;p&gt;In the last couple of months we participated in an increasing count of customer projects following current trends of agile software development approaches and corresponding toolstacks. Especially the terms &lt;em&gt;Continuous Integration&lt;/em&gt; and &lt;em&gt;Continuous Delivery&lt;/em&gt; kept (and still keep) popping up on every corner. The frameworks and processes behind those two hypes aid developing software at higher quality in shorter release cycles. This is especially relevant since end consumers nowadays expect fast releases including the newest features. If companies neglect this demand, competitors might take advantage of their better time-to-market which might result in increased market share and -dominance. A lot of changes are happening in the space of CI/CD. Existing tools become more mature, gaining increased attention, and new ones are appearing every month including better ways of integrating them into existing or new processes. Companies benefit from more choices, increased flexibility, and faster integration into existing company policies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
