Adding a stageĬI/CD processing on GitLab is done in stages. For Jekyll, all we’re going to need is Ruby. There are virtual machines for NodeJS, for PHP, for Ruby, or a combination of these, and much else. For each build, GitLab is going to launch a special virtual machine, and you get to specify what software should be present on it. The first thing GitLab needs to know is what environment to build your code in. In gitlab-ci.yml (which must live at the root of your repository), start with this: image : ruby:2.6 Without, GitLab’s CI/CD process does nothing. It’s a YAML file that tells GitLab which steps to take whenever you commit new code. In order to get CI/CD to work for you, you’ll need to add a file to your Jekyll codebase: gitlab-ci.yml. Builds and tests can fail, and GitLab will let you know with an email, if you like. In a nutshell, whenever you commit some code, a process on GitLab launches that builds that code, tests it, and even deploys it - according to your specifications.
GitLabs offers Continuous Integration / Continuous Deployment. But there’s more: it also comes with a set of tools that can build and deploy your code (that is, your website) every time you commit a change to the git repository. GitLab has the advantage that it allows you to create private repositories, free of charge. It’s always a good idea to put your code in a git repository, and store it with a service like GitHub or GitLab. Wouldn’t it be nice if that were automated?Įnter GitLabs Continuous Integration / Continuous Deployment (CI/CD). Still, having to upload the whole site through FTP every time takes a lot of work. Writing content for Jekyll is also a snap: just create some markdown, build and check your site, and you’re ready to upload. It churns out pure HTML (possibly enriched with 3rd party APIs like Disqus), so it’s fairly hackproof – unlike, say, WordPress. Jekyll is a fantastic tool to develop fast, reliable websites.
0 kommentar(er)
