Hi all,
As you all have noticed, I've been working to clean up common-lisp.net and
simplifying the administration process.
One of the things we have done is that we implemented a deployment pipeline
for the common-lisp.net main site using GitLab. It's been a great joy to
work with it so far and made deployment of new site content easier than
ever before.
*My proposal is to set up a GitLab CI based deployment pipeline* for *all
common-lisp.net <http://common-lisp.net> projects*. Meaning that I'm
proposing to import the current project pages (/project/*/public_html) into
GitLab repositories (<project-name>-site) with a gitlab-ci file which
causes the content to be published.
The approach above will mean simple import of the existing static content.
However, after import, the static output can be replaced by different input
and a static content generator, just like we did with the common-lisp.net
site.
Eager to hear your thoughts,
Erik.
I navigated to https://common-lisp.net/independent-lists and clicked on
small-cl-src. This produces the following error:
Bug in Mailman version 2.1.23 We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this information in the Mailman error logs.
I tried a few others and got the same error.
--
Ray
Hi,
I'm getting a Python exception trying to use ViewVC on my projects:
https://common-lisp.net/viewvc/tovero/trunk/
Has this changed and do I need to update my links to do SVN browsing?
Thank you!
Hi,
Can you please delete the bordeaux-threads Trac project ? I'm not using
it any more.
--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
> On Aug 1, 2020, at 22:00, Robert Goldman <rpgoldman(a)gmail.com> wrote:
>
> I'm afraid I have been very busy at work, but also the linux box I have been using as my Jenkins platform had a disk failure, taking it out of action.
[…]
> If anyone has hosting suggestions, please let me know: otherwise I'm afraid we'll be limping along till September, which is unfortunate, since we have a bunch of fixes and bug reports, and I would very much like to be able to get these wrapped up into a bug fix release.
>
> I hope you all are staying safe and healthy!
We would potentially be interested in hosting the ASDF CI on common-lisp.net with gitlab
CI. We would have to work out the kinks with using commercial CL
implementations including reaching out to Allegro and LispWorks for proper
licensing. Providing CI containers for tuned for ANSI CL implementations has
long been on our desired features, so this would line up well with where we
want to push the services offered by common-lisp.net.
It would take an unknown amount of work to provide this service to ASDF provided by an
unspecified number of volunteers, but given the importance of ASDF to everyone,
I believe we could attract a decent amount of help. If there is a decent
alternative with Travis or some other service, and just getting things running
again rather than being a guinea pig for new services is your priority, then
please pursue that path.
We have a CLF board meeting this Wednesday at 1900 UTC where I could advance such
an idea, and we could coordinate on reaching out to the commercial vendors for
(hopefully free) licensing term details.
CLF board meeting attendence is more or less open to those who wish to attend
via GOOG meet. Either drop me a mail, or stop by #common-lisp.net to get the
connection details.
--
"A screaming comes across the sky. It has happened before but there is nothing
to compare to it now."