Session
FOSDEM Schedule 2021
Continuous Integration and Continuous Deployment

ARM your continuous integration system with fruits!

D.cicd
Bruno Verachten
What if you could add a Gitlab runner to your herd for just a few bucks to alleviate your existing runners and to improve your jobs wasted time in the queue? Wouldn't it be even better if that improvement could cost nothing, because you already have everything on hand?
Being able to build/test/deploy on a remote machine each time we commit has been a major progress for us, developers. 🚀 Furthermore, by using Docker, things have been so much easier! No more dependency hell when you have to build and test two incompatible products. This solution looks almost perfect… until you reach a threshold. As your Gitlab-ci will become more and more popular within your organization, you may experience longer waiting queues until the next batch of Runners is released. So you may go from praising the CI to cursing the CI. You maybe have a Raspberry Pi taking dust on your desk or in your drawer. What’s the point? What’s the connection with the CI? Well… What if I told you you could transform this momentarily useless piece of hardware into a brand new Gitlab-ci Runner? This way, you could shorten the time your jobs spend in the queue. But wait, there is more. What if there was a cheaper solution that could allow you to create a Gitlab-ci Runner for a 15€ investment? You may have heard about Banana Pi, Orange Pi, and other variations of fruit Pi(e). The competition is harsh between these manufacturers, and you can find pretty nifty machines for darn cheap. These machine can run Docker, and even Gitlab-Runner on top of it. What if you could even build Docker images through CI on these machines? Is this even possible? It is. You shall leave this talk by knowing the basics to start your own Gitlab Runner for 15€.

Additional information

Type devroom

More sessions

2/7/21
Continuous Integration and Continuous Deployment
D.cicd
Introduction of the CI/CD devroom
2/7/21
Continuous Integration and Continuous Deployment
D.cicd
The emergence of virtualization, containers, and cloud native has resulted in tremendous advances in enabling organizations to develop new services and make them available to end users. In addition, new paradigms such as Continuous Integration (CI) and Continuous Delivery (CD) allow organisations to do this much faster than before, empowering them to go to market ahead of the competition. Despite its many advantages, the CI/CD ecosystem has its challenges. This session will discuss issues ...
2/7/21
Continuous Integration and Continuous Deployment
D.cicd
Three phrases keep popping up when talking about modern workflows and development and deployment techniques; CD, GitOps, and progressive delivery.
2/7/21
Continuous Integration and Continuous Deployment
Andrea Frittoli
D.cicd
Continuous integration and deployment (CI/CD) system are hardly ever ceaseless as the name would suggest; they do aim though to follow changes in code, configurations and versions. They often achieve that by both handling and generating events. For instance, a CD system receives an event that describes a new version of an application, and it runs a workflow in response. When the workflow starts or when it reaches completion, the CD system generates events for the benefit of other processes that ...
2/7/21
Continuous Integration and Continuous Deployment
Vlad Bogolin
D.cicd
Recently, the MariaDB Foundation has been developing a new continuous integration framework for the MariaDB Server. The goal of buildbot.mariadb.org is to ensure that each change is properly tested on all supported platforms and operating systems. Our new CI uses almost exclusively latent workers, more exactly Docker latent workers. In this talk, I will present a main overview of the CI infrastructure, the advantages of using latent workers and talk about the challenges that we encountered along ...
2/7/21
Continuous Integration and Continuous Deployment
D.cicd
When Everything as Code converges to automate/test your processes, in this talk we would like to discuss further our journey and our vision to handle our automation programmatically.
2/7/21
Continuous Integration and Continuous Deployment
Philipp Strube
D.cicd
Kubernetes, GitOps, and Infrastructure as Code are as powerful as they are popular and seem like the perfect match. Consequently, using Terraform to maintain Kubernetes clusters and resources is a very common use-case. And it requires careful integration of many moving parts, from Terraform providers and modules, to CI/CD pipelines and triggers. However, despite this being such a popular use-case, teams previously had no alternative than writing everything from scratch. On the software ...