<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 14 Oct 2020, at 13:03, Mark Evenson wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999">
<p dir="auto">On Oct 14, 2020, at 19:34, Robert Goldman <a href="mailto:rpgoldman@sift.info" style="color:#999">rpgoldman@sift.info</a> wrote:</p>
<p dir="auto">That would be great. I have a Jenkins set up on a multi-core box at SIFT that for now runs only Allegro, SBCL and CCL. It's hard for me to make it accessible to anyone else, though, because Jenkins is such a security nightmare: we keep access only to our VPN.</p>
</blockquote>
<p dir="auto">Are all the artifacts necessary to run the Jenkins pipeline in the ASDF<br>
repository? I haven’t used Jenkins in something like a decade, so I have long<br>
forgotten anything I may have remembered, but will start figuring things out<br>
tomorrow.</p>
</blockquote>
<p dir="auto">Yes, if I understand your question correctly: there are git submodules for everything that is needed to run the tests, except for the lisp implementations.</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">Running on Allegro, SBCL, CCL, ECL, and ABCL should be quite doable. I have<br>
yet to hit LispWorks up for a license, but will make the appropiate polite<br>
request when I know more about how to keep the licensing secure for Allegro in<br>
the Jenkins instance.</p>
</blockquote>
<p dir="auto">I have long had a complimentary Lispworks license, with use restricted to only testing compatibility of ASDF (and another open source library) with LW.</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">We should be able to provide somewhat of a progress report tomorrow around this<br>
time as to how far we actually got to running the ASDF CI under Jenkins.</p>
</blockquote>
<p dir="auto">In mine, I simply set the environment variables <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">ASDF_TEST_LISPS</code> and the variables that point to the lisp implementations. Then I call <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">make test-all-no-upgrades-no-stop</code>.</p>
<p dir="auto">But this is <em>not</em> the clever way to do things, if you have the ability to spawn multiple processes for concurrent testing on multiple implementations.</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">best,<br>
Mark</p>
<p dir="auto">-- <br>
"A screaming comes across the sky. It has happened before but there is nothing<br>
to compare to it now."</p>
</blockquote>
</div>
</div>
</body>
</html>