Blog2018 ≫ I set up CI on Gitlab for this blog

What does this even mean? I got continuous integration / continuous deployment working in the new repository hosting last night. Did I mention this yesterday? I think I did. Anyway, last "commit" of the day (last change to the site that I committed and sent up to Gitlab1 and it triggered some jobs. The code was tested, the blog was rebuilt, and the rebuilt version was committed back to the repo. Next job is then to push that built code back up to Amazon S3 and job's a good 'un!

I had the same old problem I had with Github that the full job to rebuild the site is just too big but if I break it down into a few steps (only rebuild the family tree if I commit a family tree change, only rebuild the gigography if I commit a gig change, etc) then it should be OK.

⬅️ :: ➡️

Paul Clarke's blog - I live in Hythe in the far South. Married + dad to two, I am a full stack web engineer, and I do js / nodejs, some ruby, other languages ect ect. I like pubs, running, eating, home-automation and other diy jiggery-pokery, history, family tree stuff, Television, squirrels, pirates, lego, + TIME TRAVEL.