![\"serverless\"](\"https:\/\/www.almtoolbox.com\/blog\/wp-content\/uploads\/\/2019\/10\/serverless.jpg\")
<\/p>\nIn short: GitLab CI\/CD lets you run your programs without the need to maintain your own computer, free of charge.<\/b><\/p>\n
<\/p>\n
A few months ago, we started distributing, to some of our customers, Excel sheets listing GitLab features. How did we create those sheets? We wrote a script, which used GitLab API to extract information from GitLab release notes and with that information we built the Excel sheet. From time to time we ran that script on one of our private computers.<\/span><\/p>\n Lately we have decided to start running our script automatically, using serverless computing on one of public clouds.<\/span><\/p>\n Serverless computing, sometimes called Function-as-a-Service (FaaS), is a cloud-computing execution model, which allows developers to run their programs without a need to take care of physical or virtual machines and other resources. Pricing is based on the actual amount of resources consumed by an application, rather than on pre-purchased units of capacity.<\/span><\/p>\n (Note that although this mode is called “serverless”, the server does exist somewhere, in a cloud provider’s data center, but users are freed from the need to manage it)<\/span>\n<\/div>\n \u00a0After some testing we have found out that for our needs we can use the serverless approach totally free of charge by exploiting GitLab shared CI runners.<\/span><\/p>\n Let’s start with the fact that GitLab allows you to create a private repository on their cloud (gitlab dot com) free of charge.<\/span><\/p>\n Moreover, GitLab provides free shared servers (“runners”) to run your programs in continuous integration (CI). That means that you can configure your GitLab project so that on every change in your Git repository, your software will run on one of GitLab-provided free servers. You can also start a CI run manually (without making any changes in the repo), schedule it in advance (like in <\/span>crontab<\/span><\/i>)\u00a0 or even trigger it by an external program using GitLab API.<\/span><\/p>\n As we said above, GitLab puts free shared CI runners at the disposal of the community. There is a limit of 2,000 minutes per month per single project, which is a significant quantity of CPU time and lets you run quite a lot of things.<\/span><\/p>\n All this means that you get serverless computing service, i.e.\u00a0 a capability to run your programs in the cloud, without worrying about CPU, memory, etc., and all that free of charge!<\/span><\/p>\n GitLab public runners are actually Docker containers, running minimal Ubuntu Linux. There is a good chance that when you will want to compile a program or run a script, you will not find there the compiler or the interpreter you need. To overcome this problem you can request a specific Docker image to be installed in your container. In addition, in the runtime you can install all necessary libraries.<\/span><\/p>\n In our case, we needed a Python interpreter plus Python modules for accessing GitLab and for writing Excel files.\u00a0 Therefore we requested that the runner be loaded with the Python image and that afterwards the above modules be installed.\u00a0<\/span><\/p>\n Below is an example of an Excel sheet created by our program:<\/span><\/p>\n In a similar way, you can run a script or test almost in any language. For example, you can test the code you have written,\u00a0 process data you have collected, deploy artifacts you have created to other servers (as an implementation of Continuous Deployment), etc.<\/span><\/p>\n We gained the ability to run a program in the cloud, without a need in having a server, whenever we want (24\/7), privately (without exposing our code to anybody), and all that free of charge!<\/span><\/p>\n Not necessarily. It is important to remember that you cannot fully rely on public free runners’ response time and performance, especially at peak times when thousands of developers from all around the world run their programs on the same servers (imagine the traffic on the Coastal Road at 8am, and you will understand what we mean). Therefore we don’t think our solution is suitable for time-critical applications.<\/span><\/p>\n You can solve the performance problem by using private runners. Those can reside either on-premises or on a public cloud. You may also prefer private runners if you need more CPU time than what you get for free, more computing power, auto-scaling, tighter security, etc.<\/span><\/p>\n You may also prefer using GitLab Enterprise edition, which provides more CI\/CD features than the free one. To learn about them, you are invited to download the above mentioned Excel file, which we built using GitLab CI…<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" In short: GitLab CI\/CD lets you run your programs without the need to maintain your own computer, free of charge. A few months ago, we started distributing, to some of our customers, Excel sheets listing GitLab features. How did we create those sheets? We wrote a script, which used GitLab API to extract information from […]<\/p>\n","protected":false},"author":10,"featured_media":4754,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[65,166,172,215],"tags":[],"class_list":["post-4752","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-case-study","category-gitlab","category-gitlab-ci","category-serverless"],"yoast_head":"\n\nWhat is Serverless Computing?<\/span><\/h4>\n
How does it work?<\/b><\/h3>\n
GitLab CI Runners<\/b><\/h3>\n
How do you create environment for running your software on public runners?<\/b><\/h3>\n
![\"gitlab-all-features\"](\"https:\/\/www.almtoolbox.com\/blog\/wp-content\/uploads\/\/2019\/10\/gitlab-all-features.jpg\")
<\/p>\nSumming up: What did we gain?<\/b><\/h3>\n
Is this solution suitable for everybody?<\/b><\/h3>\n