<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ranjan Kumar Singh</title>
    <description>The latest articles on DEV Community by Ranjan Kumar Singh (@ranjansingh41).</description>
    <link>https://dev.to/ranjansingh41</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F321893%2F23a0b3fa-b26b-4258-8195-7de3e548b442.png</url>
      <title>DEV Community: Ranjan Kumar Singh</title>
      <link>https://dev.to/ranjansingh41</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ranjansingh41"/>
    <language>en</language>
    <item>
      <title>JFrog Pipelines</title>
      <dc:creator>Ranjan Kumar Singh</dc:creator>
      <pubDate>Mon, 06 Apr 2020 07:11:54 +0000</pubDate>
      <link>https://dev.to/ranjansingh41/jfrog-pipelines-2ab</link>
      <guid>https://dev.to/ranjansingh41/jfrog-pipelines-2ab</guid>
      <description>&lt;h1&gt;
  
  
  What is JFrog Pipelines?
&lt;/h1&gt;

&lt;p&gt;JFrog Pipelines is one of the most advanced DevOps automation solutions in Today's world to perform end-to-end automation tasks of building, testing, and deploying software as part of a system of (CI/CD).&lt;/p&gt;

&lt;p&gt;Some Important concept of &lt;a href="https://jfrog.com/pipelines/"&gt;JFrog Pipelines&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Steps
&lt;/h1&gt;

&lt;p&gt;Steps are executable units that perform a specific task, such as building an application, pushing to an artifactory, Docker, AWS, GoogleCloud, etc. provisioning the machine on ubuntu_16.04, ubuntu_18.04, CentOS_7 and windowServer_2019, etc.&lt;/p&gt;

&lt;h1&gt;
  
  
  Resource
&lt;/h1&gt;

&lt;p&gt;Resource typically contains information needed for a step in a pipeline to execute and can also be used to store information produced by a step. For example source code control system (Git Repository ), Image, FileSpec, HelmChart etc.&lt;br&gt;
The available resource for Jfrog Pipelines are:&lt;br&gt;
&lt;a href="https://www.jfrog.com/confluence/display/CICD/Aql"&gt;Aql&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/BuildInfo"&gt;BuildInfo&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/DistributionRule"&gt;DistributionRule&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/FileSpec"&gt;FileSpec&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/GitRepo"&gt;GitRepo&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Image"&gt;Image&lt;/a&gt; , &lt;a href="https://www.jfrog.com/confluence/display/CICD/ReleaseBundle"&gt;ReleaseBundle&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/RemoteFile"&gt;RemoteFile&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/VmCluster"&gt;VmCluster&lt;/a&gt; and &lt;a href="https://www.jfrog.com/confluence/display/CICD/Webhook"&gt;Webhook&lt;/a&gt;. &lt;/p&gt;

&lt;h1&gt;
  
  
  Integrations
&lt;/h1&gt;

&lt;p&gt;Integrations are used to connect your Pipelines workflows to third party platforms or services and manage secrets like tokens, passwords, configuration detail that are needed for Steps in a Pipeline to interact with the source.&lt;br&gt;
All credential information is encrypted and maintained separately from the pipeline definition, and held in a secure storage.&lt;/p&gt;

&lt;p&gt;The available integration types for Jfrog Pipelines are:&lt;br&gt;
&lt;a href="https://www.jfrog.com/confluence/display/CICD/Airbrake+Integration"&gt;Airbrake&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Artifactory+Integration"&gt;Artifactory&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/AWS+Keys+Integration"&gt;AWS Keys&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Azure+Keys+Integration"&gt;Azure Keys&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Bitbucket+Integration"&gt;Bitbucket&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Digital+Ocean+Integration"&gt;Digital Ocean&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Distribution+Integration"&gt;Distribution&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Docker+Registry+Integration"&gt;Docker Registry&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/External+Webhook+Integration"&gt;External Webhook&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/File+Server+Integration"&gt;File Server&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Generic+Integration"&gt;Generic&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/GitHub+Enterprise+Integration"&gt;Github Enterprise&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/GitHub+Integration"&gt;Github&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/GitLab+Integration"&gt;Gitlab&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Google+Cloud+Integration"&gt;Google Cloud&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Internal+Webhook+Integration"&gt;Internal Webhook&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Jira+Integration"&gt;Jira&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Kubernetes+Integration"&gt;Kubernetes&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/NewRelic+Integration"&gt;Newrelic&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/PEM+Key+Integration"&gt;PEM Key&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/Slack+Integration"&gt;Slack&lt;/a&gt;, &lt;a href="https://www.jfrog.com/confluence/display/CICD/SMTP+Credentials+Integration"&gt;SMTP Credentials&lt;/a&gt; and &lt;a href="https://www.jfrog.com/confluence/display/CICD/SSH+Key+Integration"&gt;SSH Key&lt;/a&gt;.&lt;/p&gt;

&lt;h1&gt;
  
  
  Pipelines
&lt;/h1&gt;

&lt;p&gt;Pipelines is a collection of interconnected series and parallel steps to achieve an outcome.&lt;/p&gt;

&lt;h1&gt;
  
  
  Run
&lt;/h1&gt;

&lt;p&gt;Run is an instance of Pipelines execution. The Pipeline Run Logs view of Pipelines provides the facilities to view the log of execution, test results, and other information for steps in the pipeline.&lt;/p&gt;

&lt;p&gt;Unified Dashboard view of JFrog Pipelines&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--sdET5V4G--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/rzu5gsh0otk85noluxtf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--sdET5V4G--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/rzu5gsh0otk85noluxtf.png" alt="Alt Text" width="880" height="465"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can see each pipe and what is the status of its runs:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--fE9pjwtX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/bevlmijqvr16g3o5rf6y.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--fE9pjwtX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/bevlmijqvr16g3o5rf6y.png" alt="Alt Text" width="880" height="463"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And for each task:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--5zeMQHQi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/kz0rie21diiqx60i8jt3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5zeMQHQi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/kz0rie21diiqx60i8jt3.png" alt="Alt Text" width="880" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And even you can see the yml file that is used in each step:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--VtHGuZJB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/bu7kbf3rz7iq28v57hnc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--VtHGuZJB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/bu7kbf3rz7iq28v57hnc.png" alt="Alt Text" width="880" height="430"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Some of the important functionality of &lt;a href="https://www.jfrog.com/confluence/display/JFROG/Pipelines+Steps"&gt;Steps&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Generic Steps
&lt;/h1&gt;

&lt;p&gt;A generic step is for general-purpose execution. The Bash and PowerShell steps, which execute any series of shell commands you specify, are the single generic steps for Linux and Windows runtimes, respectively.&lt;/p&gt;

&lt;h1&gt;
  
  
  Native Steps
&lt;/h1&gt;

&lt;p&gt;Pipelines native steps, you only have to tell your automation server what to do, not how to do it. As part of the JFrog Platform, Pipelines natively knows the best way to publish your builds to Artifactory, as well as build and deliver release packages through Distribution. Native steps provide you quick building blocks to perform the everyday tasks that fill your Artifactory repositories.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://jfrog.com/artifactory/free-trial/?int_source=Blog%20Post"&gt;Start your free trial on JFrog Platform&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hope this helps! :)&lt;/p&gt;

</description>
    </item>
    <item>
      <title>DevOps? In Today World!</title>
      <dc:creator>Ranjan Kumar Singh</dc:creator>
      <pubDate>Sun, 26 Jan 2020 13:36:01 +0000</pubDate>
      <link>https://dev.to/ranjansingh41/devops-in-today-world-4ago</link>
      <guid>https://dev.to/ranjansingh41/devops-in-today-world-4ago</guid>
      <description>&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--6hyfnPVi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/sm7uz4ocjgd83zcxsm2t.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--6hyfnPVi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/sm7uz4ocjgd83zcxsm2t.png" alt="Alt text of image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;We have noticed that the word DevOps sparks confusion, especially for non-technical and many technical people. Sure, the word itself is a combination of two-word development and operations, but what is DevOps?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is DevOps?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The word DevOps is a combination of two words development and operations. “Dev” refers to software application development, and “Ops” refers to IT operations. DevOps is a culture that improves collaboration between Software Development and IT Operations Team to deploy code to production faster in an automated &amp;amp; repeatable way.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--6xaCDrGV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/cpkbyp9kme1giu1x5ha5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--6xaCDrGV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/cpkbyp9kme1giu1x5ha5.png" alt="Alt text of image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;DevOps process involves a lot of development, testing and deployment technologies for developing automated CI/ CD pipelines. Following are some of the famous DevOps tools:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GitHub, GitLab &amp;amp; Bitbucket – Source code management &lt;/li&gt;
&lt;li&gt;Jfrog pipelines, Jenkins &amp;amp; TeamCity – Automation server, with plugins 
built for developing CI/ CD pipelines&lt;/li&gt;
&lt;li&gt;Robotium &amp;amp; Selenium  – Automation testing&lt;/li&gt;
&lt;li&gt;Docker – Software Containerization Platform&lt;/li&gt;
&lt;li&gt;Kubernetes – Container Orchestration tool&lt;/li&gt;
&lt;li&gt;Chef, Ansible &amp;amp; Puppet  – Configuration Management and Deployment&lt;/li&gt;
&lt;li&gt;Lansweeper &amp;amp; Nagios  – Continuous Monitoring&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--0ydEwe_9--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/x8a8k5tnio4sxfazkb7h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--0ydEwe_9--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/x8a8k5tnio4sxfazkb7h.png" alt="Alt text of image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DevOps has four fundamental core values:-&lt;/strong&gt; Culture, Automation, Measurement, and Sharing.&lt;br&gt;
&lt;strong&gt;DevOps practice has five levels:-&lt;/strong&gt; values, principles, methods, practices, and tools.&lt;/p&gt;

&lt;p&gt;In any company developers, the team writes code for new products, features and bug fixes. In a traditional software development life-cycle process, it takes weeks for the Dev team’s work to be placed into production.&lt;/p&gt;

&lt;p&gt;When the Development team code is finally deployed into the Production Environment, Some time unexpected errors or problems occur. This mostly happens because the Development team is focused on writing code for its Development Environment.&lt;/p&gt;

&lt;p&gt;The Operations team is responsible for maintaining the uptime of the Production Environment. The tools that the Operation team uses to manage or administer servers might not be effective or efficient when the number of servers increases largely within the company.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--ChYfNo4e--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/vn4wetsfpxlpz6o16h4q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ChYfNo4e--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/vn4wetsfpxlpz6o16h4q.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This challenge affects how new code is deployed in the Production Environment which is why the Operations team usually requires code deployments to be scheduled and are allowed only once a month in most cases. Once the code is deployed into the Production Environment, the Operations team is responsible for error diagnoses or problems caused by the changes.&lt;/p&gt;

&lt;p&gt;Adopt DevOps require a new mindset, tools, and skills. DevOps integrates developers and operations teams in order to improve collaboration and productivity by automating infrastructure, workflow, and continuously measuring application performance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DevOps is The Secret to Doing More, Faster and Better.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DevOps can be implemented in&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Automated Testing&lt;/li&gt;
&lt;li&gt;Continuous Integration&lt;/li&gt;
&lt;li&gt;Continuous Delivery&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Automated Testing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Automated testing is a method in software testing that makes use of special software tools to control the execution of tests and then compares actual test results with predicted or expected results. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--dYALw7pX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/54hfvq6mklccflccba7u.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--dYALw7pX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/54hfvq6mklccflccba7u.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The process of using special automation tools to control the execution of software tests to compare the outcome with the expected results is called Automation Testing. It is used to reduce the testing time of complex activities like regression testing and other laborious or extensive testing processes in the software development cycle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Continuous Integration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Continuous integration -&amp;gt; CI -&amp;gt;set of processes -&amp;gt;Build pipeline/CI Pipeline&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--VXRn9sIP--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/xoh88w1uoksqqo66139b.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--VXRn9sIP--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/xoh88w1uoksqqo66139b.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Continuous integration is a DevOps software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important benefits continuous Integration&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Minimizes the human error&lt;/li&gt;
&lt;li&gt;Faster Mean Time To Resolution&lt;/li&gt;
&lt;li&gt;Smaller Backlog&lt;/li&gt;
&lt;li&gt;Increase Team Transparency and Accountability&lt;/li&gt;
&lt;li&gt;Reduce Costs&lt;/li&gt;
&lt;li&gt;Easy Maintenance and Updates&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Continuous Delivery&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Continuous delivery is the important process of delivering the Updates/software to production in smaller increments, ensuring that the software can be released at any time. The main focus and objective of continuous delivery is to build, test and release to the customer bit faster and more frequently.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--hTZypDg0--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/bdrzk9vtcc7m2uaftj7w.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--hTZypDg0--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/bdrzk9vtcc7m2uaftj7w.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important benefits continuous Delivery:-&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Lower costs&lt;/li&gt;
&lt;li&gt;Increases the number of deliveries.&lt;/li&gt;
&lt;li&gt;Low-risk releases.&lt;/li&gt;
&lt;li&gt;Minimize the risk of failure in production.&lt;/li&gt;
&lt;li&gt;Reduces manual work.&lt;/li&gt;
&lt;li&gt;Increases confidence in the team.&lt;/li&gt;
&lt;li&gt;Higher quality&lt;/li&gt;
&lt;li&gt;It enables the team to automate everything.&lt;/li&gt;
&lt;li&gt;Better products.&lt;/li&gt;
&lt;li&gt;Enables faster feedback.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Continuous Deployment&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When software is deployed quickly into production since team members make sure the application goes through complete Automation or manual testing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--34jxaIHi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/nmf6ur18zkmh9kx7wqki.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--34jxaIHi--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/nmf6ur18zkmh9kx7wqki.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DevOps Team:-&lt;/strong&gt; &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Developer (Dev)&lt;/li&gt;
&lt;li&gt;Quality Assurance (QA)&lt;/li&gt;
&lt;li&gt;Operations (System Admin, Production support)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Benefits of DevOps:-&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Shorter Development Time, Faster Innovation&lt;/li&gt;
&lt;li&gt;Reduced Deployment Failures, Rollbacks, and Time to Recover.&lt;/li&gt;
&lt;li&gt;Better Communication and Cooperation&lt;/li&gt;
&lt;li&gt;Reduce Costs and IT Staff&lt;/li&gt;
&lt;li&gt;Lower cost&lt;/li&gt;
&lt;li&gt;Reduction of Bugs&lt;/li&gt;
&lt;li&gt;Increase the rate of software delivery and faster time to market.&lt;/li&gt;
&lt;li&gt;Good processes across IT and teams, including automation.&lt;/li&gt;
&lt;li&gt;Cross-skilling and self-improvement.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thanks!!&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
