https://blog.lwolf.org/categories/ci/cd/ Recent content in ci/cd on lwolfs blog Hugo -- gohugo.io en-us Thu, 30 Jan 2020 00:00:00 +0000 https://blog.lwolf.org/post/agola-one-ci-to-run-them-all/ Thu, 30 Jan 2020 00:00:00 +0000 https://blog.lwolf.org/post/agola-one-ci-to-run-them-all/ I’ve been looking for a good Continues Integration(CI) system for quite some time now. System, that could work with all the major repository providers and run on my hardware. The need for multi-provider support comes from the fact that my code is spread across: Github Gitlab, cloud and self-hosted Gitea - I’m currently replacing my self-hosted Gitlab with it. I find it much simpler and faster. This means I can neither have a single view of all my tests nor have a unified way of testing. https://blog.lwolf.org/post/how-to-create-ci-cd-pipeline-with-autodeploy-k8s-gitlab-helm/ Thu, 30 Mar 2017 00:00:00 +0000 https://blog.lwolf.org/post/how-to-create-ci-cd-pipeline-with-autodeploy-k8s-gitlab-helm/ Since my previous posts[1][2] about CI/CD, a lot have changed. I started using Helm for packaging applications, stopped using docker-in-docker in gitlab-runner. Recently, I started working on a few Golang microservices. I decided to try gitlab’s caching and split the job into multiple steps for better feedback in UI. Few of the main changes to my .gitlab-ci.yaml file since my previous post: no docker-in-docker using cache for packages instead of a prebuilt image with dependencies splitting everything into multiple steps. https://blog.lwolf.org/post/fully-automated-gitlab-installation-on-kubernetes-including-runner-and-registry/ Mon, 27 Feb 2017 00:00:00 +0000 https://blog.lwolf.org/post/fully-automated-gitlab-installation-on-kubernetes-including-runner-and-registry/ After my previous post - How to easily deploy GitLab to Kubernetes - I’ve got a lot of responses. I helped several people to get GitLab up and running on their clusters. With that manifests it became much easier to deploy GitLab to Kubernetes. It was still few things that were usually misunderstood and misconfigured. You can find out these things only by talking with people who are actually trying to use your work. https://blog.lwolf.org/post/how-to-build-tiny-golang-docker-images-with-gitlab-ci/ Mon, 06 Feb 2017 00:00:00 +0000 https://blog.lwolf.org/post/how-to-build-tiny-golang-docker-images-with-gitlab-ci/ This post will show how to build Golang docker containers using Gitlab-CI. It’s the sequel of my previous posts about building and optimizing docker containers. I’ve written a small microservice in Golang, and I needed to configure my GitLab to auto build it. It uses Glide as a package manager for Go. My directory tree for this project looks like this: > $ tree ├── Dockerfile ├── build_base.sh ├── glide. https://blog.lwolf.org/post/how-to-speed-up-builds-and-save-time-and-money/ Thu, 01 Dec 2016 00:00:00 +0000 https://blog.lwolf.org/post/how-to-speed-up-builds-and-save-time-and-money/ In one of the previous posts, I described the way I’m using GitLab to build and test images. Despite the fact that it’s pretty simple configuration and actual tests are run for less than a minute, complete pipeline takes around 20 minutes. Which seems very unreasonable. I spent some time digging out the problem and was able to reduce build time to around 3 minutes. Here are few things, that should be considered to optimize pipeline. https://blog.lwolf.org/post/continuous-deployment-to-kubernetes-from-gitlab-ci/ Mon, 10 Oct 2016 00:00:00 +0000 https://blog.lwolf.org/post/continuous-deployment-to-kubernetes-from-gitlab-ci/ In my previous posts I described how to deploy GitLab to Kubernetes and configure GitLab-CI to build and test docker containers. In this one, I’m going to write about continues deployments. I assume that you already have Kubernetes cluster and application running, and you have some manual way of deploying your application to it. So I will not touch the basics of writing Kubernetes manifests. But I will briefly describe my own scripts and show how I configured GitLab-CI to automate deployment. https://blog.lwolf.org/post/how-to-build-and-test-docker-images-in-gitlab-ci/ Wed, 21 Sep 2016 00:00:00 +0000 https://blog.lwolf.org/post/how-to-build-and-test-docker-images-in-gitlab-ci/ In the previous post I described how to run own GitLab server with CI runner. In this one, I’m going to walk through my experience of configuring GitLab-CI for one of my projects. I faced few problems during this process, which I will highlight in this post. Some words about the project: Python/Flask backend with PostgreSQL as a database, with the bunch of unittests. React/Reflux in frontend with Webpack for bundling. https://blog.lwolf.org/post/how-to-easily-deploy-gitlab-on-kubernetes/ Thu, 08 Sep 2016 00:00:00 +0000 https://blog.lwolf.org/post/how-to-easily-deploy-gitlab-on-kubernetes/ I spent some time recently researching how to build CI/CD pipeline to automate testing and deploying. Since I’m developing everything in containers and use Kubernetes to manage it GitLab with its CI runners and recent integrations with k8s seemed like a good option. In this post, I will describe the steps needed to get GitLab with GitLab Runner, up and running on top of Kubernetes. All manifests used in this post could be found here