Thanks for reaching out , Dave. I hadn't realized that cl.net had the full gitlab CI hooked up to it. Are there any resource issues? There are a lot of projects hosted there.That said, are there sufficient resources there if we start running a pipeline?
--
Robert P. GoldmanOn October 14, 2020 at 07:21:44, Dave Cooper (david.cooper@genworks.com) wrote:
Dear Robert,Are you sure you want to use Jenkins? Gitlab has built-in CI. And the CLF has acquired Allegro CL licenses for a ASDF testing (graciously donated by Franz Inc), and we have a to-do item to attempt the same for LispWorks. If you’re willing, we would like to help set up ASDF testing pipelines as part of common-lisp.net infrastructure.If you have reasons of your own to set up a Jenkins setup and could use access to Allegro and maybe Lispworks licenses for that purpose, please reach out regarding that as well. I am not sure about any Jenkins experience among clf or cl.net volunteers, however.Please advise,Dave--
On Tue, Oct 13, 2020 at 11:06 PM Robert Goldman <rpgoldman@sift.info> wrote:Does anyone have expertise configuring Jenkins to run against a remote Gitlab install?
If so, would you please reach out to me? I have finally restored some of my CI support for ASDF, but I don't know how to set up my Jenkins to run against merge requests on Gitlab (if that is even possible).
I have a backlog of patches that I would like to get evaluated and merged, but could use some help with the automation.
Thanks!