<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><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:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Unless you are actively working on Trove, this is something you wouldn’t care about so here’s the TL;DR<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='text-indent:.5in'>The changes to the Trove CI (including trove, trove-integration, and python-troveclient) related to the project to get rid of trove-integration are now complete. Thanks to everyone in infra for the reviews, suggestions, and help along the way.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The details if you care …<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For some time now we’ve been working in Trove on a project to get rid of the trove-integration repository. Now, before you get your expectations up, it isn’t going to be deleted anytime soon. It will continue to be used for the stable branches (liberty, mitaka and newton) which means that when Queen is released and Newton gets mothballed, we can finally get rid of the repository.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the meanwhile, changes to trove-integration will be very limited and only those things that matter to the stable branches in question. We will therefore apply the same kind of high bar that we would to changes that impact the stable branches. Bearing in mind that trove-integration is not branched, scrutiny will be fairly high.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All the things you know and love in trove-integration have been merged into the trove repository and I’m continue to work on cleaning it up here. This is an ongoing project, and since the bits now in trove are being used in the CI, changing it needs to be done with care as it could end up destabilizing master and making it hard for everyone.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If you find some egregious problem in the merge into trove, or if something has broken that requires immediate attention, please do not hesitate to contact me. On the other hand, if you find some typos in the artifacts that came from trove-integration into trove, or you’d like to do something that is not critical or urgent, I’d request you to let me know so that we don’t end up stomping on each other’s changes, and making merge nightmares for everyone.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the even smaller number of you who read this, and who give a damn about the trove CI jobs, please note that jobs with the words “integration” or “legacy” in the name are intended for running only on stable/(liberty|mitaka|newton) and will likely have a counterpart which does not have those words in the name. Those jobs are intended for master (i.e. Ocata and later). There is also a weird name collision that we ended up with that has resulted in a somewhat awkward change in zuul/layout.yaml which uses a skip-if in a somewhat peculiar way. If you want to wander near that and make changes, be warned, there be gotchas there. If in your reviewing, you notice a job running on trove/master or troveclient/master or a stable branch Ocata and forward that includes the words legacy or integration, you can be sure there’s a problem.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All seems to be good now, several test jobs have done well, let’s see if it holds up. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-amrith<o:p></o:p></p></div></body></html>