<!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 15 Oct 2020, at 12:19, Mark Evenson wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">@Robert: would it be satisfactory to have the output of the ASDF tests<br>
available in a non-Jenkins environment? Do we need to run the ADSF tests under<br>
OSs other than Linux, that is do you current test other environment likes<br>
macOS/Windows/FreeBSD?</p>
</blockquote>
<p dir="auto">I got started with Jenkins only because my company had it, and so I was familiar with it, but hadn't used the GitLab/GitHub frameworks. I'm not ready to configure GL/GH style CI myself, beyond crude bug fixing, but I am quite comfortable with it. Indeed, I believe it's simpler, because it can be merge request aware, but doing that with Jenkins requires additional work.</p>
<p dir="auto">[One cranky request --- if we set this up in that way, please use <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">gitlab-ci.yml</code> or some other <em>visible</em> filename, instead of the dotted filenames that are hidden by default. I'm not sure why people think hiding critical configurations is a good idea, but I don't. Thanks!]</p>
<p dir="auto">I currently run the ASDF tests on MacOS, but not using Jenkins, only doing it by hand (since that's what my laptop runs). So running MacOS automatically would be a nice-to-have, but is not critical.</p>
<p dir="auto">I currently <em>don't</em> run the ASDF tests on Windows, but I should, since it's such a different platform. Dave Cooper has kindly offered me access to a Windows VM for testing, but I haven't gotten around to setting it up. It would be lovely if we could hook Windows testing into whatever CI framework we end up with.</p>
</div>
</div>
</body>
</html>