<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div><br></div>
<div><br></div>
<div>On Tue, Aug 22, 2017, at 04:15 PM, Chris Davies wrote:<br></div>
<blockquote type="cite"><blockquote type="cite"><div>* regarding CI - have working setup with cyrus.works, but it has issues with manual work needed for libs update.<br></div>
</blockquote><div><br></div>
<div>Changes pushed to git will be picked up by cyrus.works. Cyrus.works runs <a href="https://github.com/cyrusimap/cyrus-docker">Cyrus docker images</a>. Occasionally these will need to be updated. Anyone with Git access can do this. I believe these were originally created by Kolab but I’m happy to maintain the ones we need for Cyrus.works.<br></div>
<div><br></div>
<div>We cache some things that rarely change to improve the build performance. This brings the build time down from about 34 minutes to about 15. This cache is automatically cleared once a week.<br></div>
<div><br></div>
<div>We had plans to expose the ability to clear that cache via Slack and those plans have been put on hold while we explore Travis CI.<br></div>
<div><br></div>
<div><br></div>
<blockquote type="cite"><div> - Relies heavily on Chris right now.<br></div>
</blockquote><div>We're working to transfer knowledge to Partha.<br></div>
</blockquote><div>I'm working on this with Chris.<br></div>
<div><br></div>
<blockquote type="cite"><div><br></div>
<blockquote type="cite"><div> - many of the scripts are known only to Chris.<br></div>
</blockquote><div><br></div>
<div>What scripts are these?<br></div>
<div><br></div>
</blockquote><div>scripts/configuration that like the error parsing for example. But as I mentioned in the weekly, you've been educating me (and Ellie on occasions) about these.<br></div>
<div><br></div>
<blockquote type="cite"><blockquote type="cite"><div> - wants to know if can completely get rid of Jenkins and use Travis completely?<br></div>
</blockquote><div><br></div>
<div>We're currently gathering requirements for Cyrus test infrastructure. Once we're satisfied with that list we'll see what technology we need and create a plan.<br></div>
</blockquote><div>Agreed. We have advantages(and limitations) from both Jenkins and Travis, we just need to figure out the path to least overheads(maintenance, infrastructure etc.)<br></div>
<div><br></div>
</body>
</html>