Dave Cooper (@dcooper) on GitLab, 2018-10-22.
Short of hosting a full-blown CL Continuous Integration setup, I think we should at least add a handful of CL implementations to our default build pipeline, to avoid nasty surprises like what happened earlier today, where something passes our default pipeline with the single implementation currently there, then proceeds to fail almost everywhere else. This does not give a nice feeling to anyone who might happen to clone our repo and try building the site locally. Even if they try it once just for fun, if such a thing is their first experience, then that may be the last time they even try.
Does anyone know if there a way we can leverage some other efforts for achieving this, such as cl-travis? (I have to admit knowing next to nothing about Travis and CL-Travis so far...)
Dave Cooper (@dcooper) on GitLab, 2018-10-22.
Apparently Roswell is the shiznit, as far as keeping up to date implementations.
Dave Cooper (@dcooper) on GitLab, 2026-10-01.
The site no longer has a portable generator for visitors to build with
whatever Lisp they have. It is a single system deployed in one image, and its
CI (load-and-smoke) loads it cold in exactly that image, then asks for every
page and every internal link. Testing it across implementations would test a
configuration nobody runs. Closing.
Sign in to comment.