<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:Calibri;}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:Calibri;
color:windowtext;}
span.msoins
{mso-style-name:msoins;
color:teal;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Jason,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Cool! I’m thinking that we’d probably be forking AS based upon our own codebase because of some pretty minor local customizations that are set up as plugins. We have some things that change layouts, changes
to exporters, etc., and we want to do our due diligence in making sure that we’re not unexpectedly breaking something with each new release. Thought we could do it through automated methods rather than checking each plugin by hand each time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-Patrick<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black"><archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Jason Loeffler <j@minorscience.com><br>
<b>Reply-To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Date: </b>Friday, July 28, 2017 at 9:22 PM<br>
<b>To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] Travis CI and ArchivesSpace<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div id="compose-container">
<div>
<div>
<p class="MsoNormal">Hi Patrick, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I use a CI test harness regularly with Drupal development. Are you looking to fork AS and customize your code base and deploy that or do you simply want to write tests for the existing production branch?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">-- <br>
Jason Loeffler<br>
Technology Consultant | The American Academy in Rome<br>
Minor Science | Application Development & Metadata Strategy<br>
Brooklyn, New York<br>
<a href="mailto:jason@minorscience.com">jason@minorscience.com</a><br>
(347) 405-0826<br>
minorscience (Skype)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">_____________________________<br>
From: Galligan, Patrick <<a href="mailto:pgalligan@rockarch.org">pgalligan@rockarch.org</a>><br>
Sent: Friday, July 28, 2017 16:07<br>
Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<br>
<br>
<br>
<span style="font-family:"Times New Roman""><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hey List,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’m pretty new to Continuous Integration and scripted testing, so I thought I’d email the list. Anyone using TravisCI to create automated tests and to integrate with their ArchivesSpace production? I’m trying
to up our software deployment game and could use some tips and tricks if you have them.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Let me know!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Patrick Galligan</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Rockefeller Archive Center</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>