<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ci/Cd on DevopsTrain</title>
    <link>https://devopstrain.lifeisfile.com/tags/ci/cd/</link>
    <description>Recent content in Ci/Cd on DevopsTrain</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©, Alex Babochkin</copyright>
    <lastBuildDate>Sun, 11 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstrain.lifeisfile.com/tags/ci/cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Do you always need CI/CD? </title>
      <link>https://devopstrain.lifeisfile.com/post/cd/</link>
      <pubDate>Sun, 11 Aug 2024 00:00:00 +0000</pubDate>
      
      <guid>https://devopstrain.lifeisfile.com/post/cd/</guid>
      <description>
        
          
            From my point of view, if a service is updated regularly, then you really can&#39;t do without it, because deploying manually is no fun at all. However, dragging these practices everywhere is also wrong.
〰️ Let me give an example: we have a utility service (not the one that&#39;s part of the application, but an auxiliary/infrastructure one) that gets updated once a year at best. And usually one or two people handle it.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
