<?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 &amp; GitOps on Tuna Cinsoy</title><link>https://tunacinsoy.com/areas/cicd/</link><description>Recent content in CI/CD &amp; GitOps on Tuna Cinsoy</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Fri, 20 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://tunacinsoy.com/areas/cicd/index.xml" rel="self" type="application/rss+xml"/><item><title>Git</title><link>https://tunacinsoy.com/posts/git/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/git/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What&amp;rsquo;s the categorization method that should be used for Issues in Github?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Issues can be categorized based on their &lt;strong&gt;statuses, priorities, types and languages&lt;/strong&gt;.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Status Labels (Process - Blues/Greens)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;status: triage&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;c5def5&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;New issue awaiting review&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;status: in-progress&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;2188ff&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Currently being worked on&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;status: done&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;0e8a16&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Completed tasks&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;status: blocked&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;b60205&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Waiting on external factors&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Priority Labels (Urgency - Reds/Oranges)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;priority: high&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;d93f0b&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Urgent, fix immediately&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;priority: medium&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;fbca04&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Normal priority&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;priority: low&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;f9c513&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Low priority&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Type Labels (Category - Purples/Pastels)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;type: bug&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;d73a4a&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Something is broken&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;type: feature&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;a2eeef&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;New functionality&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;type: maintenance&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;7057ff&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Tech debt, chores, refactoring&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Infrastructure as Code Labels&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;iac: terraform&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;7b42bc&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Terraform configurations (.tf)&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;iac: bicep&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;0078d4&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Azure Bicep templates (.bicep)&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Post a comment with the Jira link, apply the status: moved-to-jira label, and immediately close the GitHub issue&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gh label create &lt;span class="s2"&gt;&amp;#34;status: moved-to-jira&amp;#34;&lt;/span&gt; --color &lt;span class="s2"&gt;&amp;#34;d4c5f9&amp;#34;&lt;/span&gt; --description &lt;span class="s2"&gt;&amp;#34;Tracking in Jira - closed on GitHub&amp;#34;&lt;/span&gt; --force
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) How to update local branches, when some of the remote branches were deleted?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>GitHub Actions</title><link>https://tunacinsoy.com/posts/github-actions/</link><pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/github-actions/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What&amp;rsquo;s a workflow file, that is used to create automation pipelines?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A GitHub Actions workflow is a simple YAML file that contains the build steps. We must create this workflow in the &lt;code&gt;.github/workflows&lt;/code&gt; directory within the repository. Versioning can be achieved by the following &lt;code&gt;build.yaml&lt;/code&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Q) What&amp;rsquo;s a sample workflow for building a docker image?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Following workflow file build a docker image which has &lt;code&gt;version&lt;/code&gt;, &lt;code&gt;timestamp&lt;/code&gt; and &lt;code&gt;commit_hash&lt;/code&gt; attached to its name for distinction purposes - and then pushes the image to dockerhub.&lt;/p&gt;</description></item><item><title>Jenkins</title><link>https://tunacinsoy.com/posts/jenkins-kaniko/</link><pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/jenkins-kaniko/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What is Jenkins?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Jenkins is a widely used automation server that helps automate various tasks, particularly those related to building, testing, and deploying software. It is open-source and Java-based tool with a plugin-based architecture that supports several integrations with source code management (git), and artifact repository (nexus, artifactory), and with also build tools such as ant, maven, gradle.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) What is Kaniko?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster. kaniko doesn&amp;rsquo;t depend on a Docker daemon and executes each command within a Dockerfile completely in userspace. This enables building container images in environments that can&amp;rsquo;t easily or securely run a Docker daemon, such as a standard Kubernetes cluster.&lt;/p&gt;</description></item><item><title>CI/CD - Argo CD</title><link>https://tunacinsoy.com/posts/ci-cd/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/ci-cd/</guid><description>&lt;p&gt;&lt;strong&gt;Q) Why Continuous Integration is not enough solely?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;CI is the first thing most organizations implement when they embrace DevOps, but things don’t end with CI, which only delivers a tested build in an artifact repository. Instead, we would also want to deploy the artifact to our environments.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) How can we describe/define Continuous Delivery?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;continuous delivery&lt;/strong&gt;, standard tooling can deploy code to higher environments based on certain gate conditions. CD pipelines will trigger when a tested build arrives at the artifact repository or, in the case of GitOps, if any changes are detected in the Environment repository. Environment repository will contain terraform files, kubernetes deployment files etc. (files that are related with environment infrastructure). When an artifact (image) is created successfully, new image tags should be updated in related k8s deployment files. &lt;strong&gt;Continuous delivery enables your team to deliver tested code in your environment based on a human trigger.&lt;/strong&gt; So, while you don’t have to do anything more than click a button to do a deployment to production, it would still be initiated by someone at a convenient time (a maintenance window).&lt;/p&gt;</description></item></channel></rss>