I intend to re-write it in the near future to make it more flexible.In my previous articles, I have explained how you can setup Magento stack, LAMP stack and Joomla in AWS. (Note: This version of the code is very static. We’ll also be able to spin it up and down as required and be guaranteed that it will be exactly the same every time.īelow is a quick configuration I put together to demonstrate how this can be done using Terraform. As a result, we’ll have visibility of every revision of our Runner’s configuration. We live in a DevOps world, surely there’s a way we can automate this process! Automated (Terraform) methodĪutomating the deployment of our Runner not only makes our lives easier, but it also enables us to take an Infrastructure as Code (IaC) approach to the deployment. Looking at the /etc/gitlab-runner/config.toml file on our Runner container, as well as the /srv/gitlab-runner/config/config.toml file of our CoreOS instance, we see that the config was generated automatically for us:Īnd there we have it! Our Runner is good to go… But let’s not stop here. If we take a look at our logs now, we should see that the Runner has successfully started, as per the last line in the output below: Feel free to start it, but if it's running already the config should be automatically reloaded! Please enter the default Docker image (e.g. Please enter the executor: parallels, shell, ssh, virtualbox, docker+machine, kubernetes, docker, docker-ssh, docker-ssh+machine: Whether to lock the Runner to current project : Please enter the gitlab-ci tags for this runner (comma separated): Please enter the gitlab-ci description for this runner: Please enter the gitlab-ci token for this runner: Please enter the gitlab-ci coordinator URL (e.g. Sudo docker exec -it gitlab-runner /bin/bash Performing the above steps looks like this: Entering the “Specific Runners” data we retrieved earlier.Issuing the gitlab-runner register command.We could put a configuration together ourselves by looking at the advanced configuration documentation, but that may be a little too advanced for newcomers. This is because the Runner is expecting to find its configuration on our host at /srv/gitlab-runner/config.toml and /etc/gitlab-runner/config.toml on our container. builds=0ĮRROR: Failed to load config stat /etc/gitlab-runner/config.toml: no such file or directory builds=0 Starting multi-runner from /etc/gitlab-runner/config.toml.
0 kommentar(er)
