CI/CD toolchains and lispworks
"Eben Bruyns (as eben at sdk dot co dot nz)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <CAEPc2HfLA9pjp57BUUVEd2M-azvp3Y3iZt9-CxinvKb3Q_x5rg@mail.gmail.com> |
Hi, Currently I have a makefile that uses some tooling I've built in lispworks to allow me to automate my build and delivery. I'm about to set up branches in my git repo to correlate to build channels I have built into my delivered systems, I have a way within my software to update itself from different delivery channels like stable, test, beta and dev. I'd ideally like to have something that I run on a cloud server (because uploads to my CDN will be much faster due to the slow internet I have on the boat). I'm just looking to see what people in Lispworks land uses around this before I reinvent the wheel. My current solution works well, but obviously now that I'm starting to roll this product out into the real world I'd like my delivery mechanisms to grow up a bit and be more robust. The main thing I'm trying to force on myself is better branch management and commits (so I can track them for release notes). It's been fantastic to move rapidly with lisp and I've been hyper productive compared to stuff I've used in the past, but I feel I have to build a few old disciplines in a new way now. Being able to fix a bug, test it in the repl and push a button that kicks a build out to the cloud delivery within minutes of it being reported is fantastic, but I can see this ending in tears one day. Regards, Eben Bruyns