<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:28:09 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-31778] Test master with WiredTiger develop</title>
                <link>https://jira.mongodb.org/browse/SERVER-31778</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;This ticket is to add a variant to &lt;tt&gt;evergreen.yml&lt;/tt&gt; in master that tests against the &lt;tt&gt;develop&lt;/tt&gt; branch in WiredTiger.&lt;/p&gt;

&lt;p&gt;The goal is to provide early signal on WT changes before we import them into &lt;tt&gt;master&lt;/tt&gt; and other branches.&lt;/p&gt;</description>
                <environment></environment>
        <key id="381861">SERVER-31778</key>
            <summary>Test master with WiredTiger develop</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="13201">Fixed</resolution>
                                        <assignee username="luke.chen@mongodb.com">Luke Chen</assignee>
                                    <reporter username="ramon.fernandez@mongodb.com">Ramon Fernandez Marina</reporter>
                        <labels>
                    </labels>
                <created>Mon, 8 May 2017 11:26:45 +0000</created>
                <updated>Mon, 30 Oct 2023 23:10:51 +0000</updated>
                            <resolved>Mon, 29 Jan 2018 01:10:46 +0000</resolved>
                                                    <fixVersion>3.7.2</fixVersion>
                                    <component>WiredTiger</component>
                                        <votes>1</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="1787537" author="ian@10gen.com" created="Mon, 29 Jan 2018 13:32:21 +0000"  >&lt;p&gt;I don&apos;t think we need to change anything - just giving &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=tess.avitabile&quot; class=&quot;user-hover&quot; rel=&quot;tess.avitabile&quot;&gt;tess.avitabile&lt;/a&gt; a heads up that this landed and any failures on the new buildvariant can probably be sent straight to &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=backlog-server-execution&quot; class=&quot;user-hover&quot; rel=&quot;backlog-server-execution&quot;&gt;backlog-server-execution&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="1787220" author="luke.chen" created="Mon, 29 Jan 2018 01:07:24 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ian.whalen&quot; class=&quot;user-hover&quot; rel=&quot;ian.whalen&quot;&gt;ian.whalen&lt;/a&gt; The changes just landed into master branch. Failures specific to the 2 new &lt;tt&gt;WiredTiger develop&lt;/tt&gt; variants are expected to go to WiredTiger team. Will BB process needs to be updated to reflect this change? &lt;/p&gt;</comment>
                            <comment id="1787219" author="xgen-internal-githook" created="Mon, 29 Jan 2018 00:58:55 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;email&apos;: &apos;luke.chen@mongodb.com&apos;, &apos;name&apos;: &apos;Luke Chen&apos;, &apos;username&apos;: &apos;lukech&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-31778&quot; title=&quot;Test master with WiredTiger develop&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-31778&quot;&gt;&lt;del&gt;SERVER-31778&lt;/del&gt;&lt;/a&gt; Test master with WiredTiger develop&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/055b329dbd215d5020c34aa1696b4186abcfc9f4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/055b329dbd215d5020c34aa1696b4186abcfc9f4&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1778890" author="ian@10gen.com" created="Fri, 19 Jan 2018 12:48:37 +0000"  >&lt;p&gt;agreed, I&apos;m really excited about this!&lt;/p&gt;</comment>
                            <comment id="1778633" author="luke.chen" created="Fri, 19 Jan 2018 03:20:59 +0000"  >&lt;p&gt;Ram&#243;n helped to point out the &lt;tt&gt;wtdevelop&lt;/tt&gt; directory (from wiredtiger git repo) does not contain &lt;tt&gt;SConscript&lt;/tt&gt; and &lt;tt&gt;build_*&lt;/tt&gt; directories which are essential for MongoDB build. The solution is to selectively copy those source code directories from &lt;tt&gt;wtdevelop&lt;/tt&gt; to &lt;tt&gt;wiredtiger&lt;/tt&gt; directory. &lt;/p&gt;

&lt;p&gt;Here is the successful patch build  (&lt;a href=&quot;https://evergreen.mongodb.com/version/5a61693dc9ec44723d001d1f&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/version/5a61693dc9ec44723d001d1f&lt;/a&gt;) for the 2 new WiredTiger develop variants:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;~ Linux DEBUG WiredTiger develop&lt;/li&gt;
	&lt;li&gt;~ Enterprise Windows 2008R2 WiredTiger develop&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="1772572" author="luke.chen" created="Fri, 12 Jan 2018 11:33:13 +0000"  >&lt;p&gt;After another discussion with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ramon.fernandez&quot; class=&quot;user-hover&quot; rel=&quot;ramon.fernandez&quot;&gt;ramon.fernandez&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alexander.gorrod&quot; class=&quot;user-hover&quot; rel=&quot;alexander.gorrod&quot;&gt;alexander.gorrod&lt;/a&gt; and I were well convinced to start with the solution of adding a couple of new &lt;tt&gt;wtdevelop&lt;/tt&gt; variants in &lt;tt&gt;mongodb-mongo-master&lt;/tt&gt; project, which has the benefits of less efforts, relatively less noise to BB (and reuse of BB tools), ease of failure correlation (by comparing with other non-wtdevelop variants), etc. Though not providing full-run capability (all mongodb-mongo-master variants) with wtdevelop codebase, it is a good starting point we can get to implement quickly, and evaluate later based on team experiences. Thanks much &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ramon.fernandez&quot; class=&quot;user-hover&quot; rel=&quot;ramon.fernandez&quot;&gt;ramon.fernandez&lt;/a&gt;!&lt;/p&gt;</comment>
                            <comment id="1763982" author="ramon.fernandez" created="Wed, 3 Jan 2018 16:36:38 +0000"  >&lt;p&gt;In terms of setup, my gut feeling is that having a forked repo and a new Evergreen project is an overly complicated setup, since I believe we can achieve what we need with just a new variant (maybe two if we wanted to test Windows as well) in the existing repo.&lt;/p&gt;

&lt;p&gt;When I first started this work, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt;&apos;s suggestion was to (and I&apos;m paraphrasing here) make better groups of tests and then use those groups in different variants to simplify maintenance and have comprehensive coverage. My initial patch worked, but didn&apos;t do any test fine-tuning or cleanup of tasks/groups.&lt;/p&gt;
</comment>
                            <comment id="1758416" author="luke.chen" created="Fri, 22 Dec 2017 04:02:38 +0000"  >&lt;p&gt;I discussed with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alexander.gorrod&quot; class=&quot;user-hover&quot; rel=&quot;alexander.gorrod&quot;&gt;alexander.gorrod&lt;/a&gt; about test set required:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;those critical &lt;tt&gt;!&lt;/tt&gt; and important &lt;tt&gt;*&lt;/tt&gt; variants in &lt;tt&gt;MongoDB (master)&lt;/tt&gt; Evergreen project are needed for an once-per-day run&lt;/li&gt;
	&lt;li&gt;other normal variants might be needed depending on the WiredTiger changes, and can be un-scheduled by default&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;It would be clear to have a new Evergreen project created for the WiredTiger develop branch testing:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;use a fork repo of MongoDB, e.g. &lt;a href=&quot;https://github.com/wiredtiger/mongo-wiredtiger-evg&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/wiredtiger/mongo-wiredtiger-evg&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;use master branch of the fork repo&lt;/li&gt;
	&lt;li&gt;use etc/evergreen.yml of the fork repo as config file&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In order to keep up with periodic variant/task updates of etc/evergreen.yml in &lt;tt&gt;MongoDB (master)&lt;/tt&gt; Evergreen project, we are thinking of writing a script to do below tasks against the fork repo, and let it run once-per-hour:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;rollback local changes (if any)&lt;/li&gt;
	&lt;li&gt;update master branch to be up-to-date with upstream (pulling latest changes of MongoDB master branch, including etc/evergreen.yml)&lt;/li&gt;
	&lt;li&gt;apply WiredTiger code changes (pulling latest changes of WiredTiger develop branch into src/third_party/wiredtiger/)&lt;/li&gt;
	&lt;li&gt;make etc/evergreen.yml adjustments (local changes), similar as Ramon&apos;s change for RHEL6.2 variant, but applies &lt;tt&gt;wtdevelop&lt;/tt&gt; module to all variants, also make &lt;tt&gt;!&lt;/tt&gt; and &lt;tt&gt;*&lt;/tt&gt; variants scheduled once per day, other variant un-scheduled&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ramon.fernandez&quot; class=&quot;user-hover&quot; rel=&quot;ramon.fernandez&quot;&gt;ramon.fernandez&lt;/a&gt;, your comments are very welcome.&lt;/p&gt;</comment>
                            <comment id="1713779" author="michael.cahill" created="Tue, 31 Oct 2017 17:56:48 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ian.whalen&quot; class=&quot;user-hover&quot; rel=&quot;ian.whalen&quot;&gt;ian.whalen&lt;/a&gt;, I think we could just convert this to a SERVER ticket, make sure &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt; is a reviewer and get on with it.  I doubt that anyone who hasn&apos;t already participated here will have an opinion about this work.&lt;/p&gt;</comment>
                            <comment id="1713704" author="ramon.fernandez" created="Tue, 31 Oct 2017 17:16:40 +0000"  >&lt;p&gt;Tentatively assigning this to &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=luke.chen&quot; class=&quot;user-hover&quot; rel=&quot;luke.chen&quot;&gt;luke.chen&lt;/a&gt; after a conversation with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=michael.cahill&quot; class=&quot;user-hover&quot; rel=&quot;michael.cahill&quot;&gt;michael.cahill&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Luke, there&apos;s a code review above that should be a reasonable starting point (in terms of Evergreen mechanics). The rest of the work is coming up with a sane subset of changes to the test subset. I&apos;d argue that we should not let best be the enemy of good here and just start testing the subset in that code review, then iterate, but now it&apos;s up to you to convince people this is a good way forward &amp;#8211; good luck &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;
</comment>
                            <comment id="1618492" author="alexander.gorrod" created="Tue, 11 Jul 2017 06:38:54 +0000"  >&lt;blockquote&gt;&lt;p&gt;Just to mention it explicitly: The existing Evergreen stepback semantics around the manifest should give you this behavior&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Nifty - is that to ensure builds work with the enterprise modules?&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;does that mean you&apos;d want a Windows version (--dbg=on or otherwise) as well?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Ideally, but any step in this direction is going to be helpful, so if that makes more work, I&apos;m happy not to include it for now.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;If you&apos;re concerned about needing to maintain an explicitly list of tasks&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Your suggestion makes sense to me.&lt;/p&gt;</comment>
                            <comment id="1617372" author="max.hirschhorn@10gen.com" created="Mon, 10 Jul 2017 05:42:27 +0000"  >&lt;blockquote&gt;
&lt;p&gt;1) It will allow the WiredTiger team to see test failures uncovered only by MongoDB tests closer to when the commit that triggered them is made. Which makes it much faster to isolate the root cause, and reduces the risk that we end up with bad storage changes in master.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Just to mention it explicitly: The existing Evergreen stepback semantics around the manifest should give you this behavior, as earlier versions of the wiredtiger/wiredtiger/develop branch would have been associated with earlier mongodb/mongo/master commits on the 1-hour batchtime builders and them stepping back.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;2) It will mean there is less manual work that needs to be done prior to updating the version of WiredTiger in MongoDB - to that end I&apos;d ideally like this target to run on all the &lt;b&gt;!&lt;/b&gt; variants.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alexander.gorrod&quot; class=&quot;user-hover&quot; rel=&quot;alexander.gorrod&quot;&gt;alexander.gorrod&lt;/a&gt;, does that mean you&apos;d want a Windows version (&lt;tt&gt;&amp;#45;&amp;#45;dbg=on&lt;/tt&gt; or otherwise) as well?&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I agree that excluding MMAPv1 tasks would be nice. I used to maintain a set of WiredTiger specific test cases, but it&apos;s difficult to maintain as test names and suites evolve over time. As with all automated testing there is tension between missing test coverage and wasting testing resources. Maintaining a manual set of tasks leads to quite a high level of risk that we won&apos;t get the best test coverage possible.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;If you&apos;re concerned about needing to maintain an explicitly list of tasks, then my suggestion would be to define a YAML anchor for the list of tasks run on the &quot;Enterprise RHEL 6.2 (inMemory)&quot; builder and then &lt;em&gt;cheat&lt;/em&gt; by having the &quot;Enterprise RHEL 6.2 WiredTiger develop&quot; builder&apos;s &lt;tt&gt;${test_flags&lt;/tt&gt;} expansion set &lt;tt&gt;&amp;#45;&amp;#45;storageEngine=wiredTiger&lt;/tt&gt; to ensure we don&apos;t run with the MMAPv1 storage engine. I typically request engineers add new tasks to the &quot;Enterprise RHEL 6.2 (inMemory)&quot; builder so I&apos;m less worried about failing to maintain that list. (See &lt;a href=&quot;https://mongodbcr.appspot.com/134660001/diff/1/etc/evergreen.yml#newcode5739&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;this code review comment&lt;/a&gt; for my canonical list of build variants.)&lt;/p&gt;</comment>
                            <comment id="1617345" author="alexander.gorrod" created="Mon, 10 Jul 2017 04:08:24 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ramon.fernandez&quot; class=&quot;user-hover&quot; rel=&quot;ramon.fernandez&quot;&gt;ramon.fernandez&lt;/a&gt; - the approach looks good to me.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt; asked some philosophilcal questions in the code review, I&apos;m going to give my opinion here:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;My impression is that we&apos;re going to run a patch build against this build variant before doing the WiredTiger import, so I&apos;m not sure there&apos;s a reason to make this too often.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;The reasons I&apos;d like to have this variant run regularly in Evergreen are three fold:&lt;br/&gt;
1) It will allow the WiredTiger team to see test failures uncovered only by MongoDB tests closer to when the commit that triggered them is made. Which makes it much faster to isolate the root cause, and reduces the risk that we end up with bad storage changes in master.&lt;br/&gt;
2) It will mean there is less manual work that needs to be done prior to updating the version of WiredTiger in MongoDB - to that end I&apos;d ideally like this target to run on all the &lt;b&gt;!&lt;/b&gt; variants.&lt;br/&gt;
3) It brings automated testing integration for the WiredTiger project one step closer.&lt;/p&gt;

&lt;p&gt;I&apos;d request that it is run daily, since there are generally less than 5 commits into WiredTiger develop each day. Or even more ideally triggered by commits into WiredTiger develop, but at most once every 8 hours.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;I don&apos;t think we want to run everything that Enterprise RHEL 6.2 runs because&lt;br/&gt;
that includes tasks which run with the MMAPv1 storage engine. I would have liked&lt;br/&gt;
to recommend the set of tasks we use for the InMemory storage engine&lt;br/&gt;
(&lt;a href=&quot;https://github.com/mongodb/mongo/blob/r3.5.9/etc/evergreen.yml#L8078-L8152&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/blob/r3.5.9/etc/evergreen.yml#L8078-L8152&lt;/a&gt;) as&lt;br/&gt;
an alternate starting point; however, due to how some of the Evergreen task&lt;br/&gt;
dependencies work, we aren&apos;t consistent about using the &quot;_WT&quot;-suffixed tasks in&lt;br/&gt;
that list so some manual fix-up would be required.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I agree that excluding MMAPv1 tasks would be nice. I used to maintain a set of WiredTiger specific test cases, but it&apos;s difficult to maintain as test names and suites evolve over time. As with all automated testing there is tension between missing test coverage and wasting testing resources. Maintaining a manual set of tasks leads to quite a high level of risk that we won&apos;t get the best test coverage possible.&lt;/p&gt;</comment>
                            <comment id="1616797" author="ramon.fernandez" created="Fri, 7 Jul 2017 22:35:37 +0000"  >&lt;p&gt;FTR, my suggested change only addresses correctness. I&apos;ll look at sys-perf next week.&lt;/p&gt;</comment>
                            <comment id="1575657" author="alexander.gorrod" created="Fri, 19 May 2017 18:11:41 +0000"  >&lt;p&gt;That makes me a bit sad - it would be helpful to have the functionality available leading up to the 3.6 code freeze deadline, but I understand we missed the project planning boat.&lt;/p&gt;</comment>
                            <comment id="1575337" author="ian@10gen.com" created="Fri, 19 May 2017 13:55:37 +0000"  >&lt;p&gt;@watchers on this ticket: The Perf team has discussed and believes that the work necessary to accomplish this is uncertain enough in scope that it should go into the Project backlog and get prioritized/scheduled like any other work there.  That means we&apos;ll come back to prioritizing this in the mid-July planning session unless someone gives a shout that this should get prioritized up.&lt;/p&gt;</comment>
                            <comment id="1567344" author="alexander.gorrod" created="Mon, 8 May 2017 21:27:04 +0000"  >&lt;blockquote&gt;&lt;p&gt;Which projects?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;The WiredTiger sys-perf jobs are the ones we are most interested in. An example of the last patch build I ran is:&lt;br/&gt;
&lt;a href=&quot;https://evergreen.mongodb.com/version/59034a432fbabe26f5006754#?59034a432fbabe26f5006754=3.2.12-Baseline&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/version/59034a432fbabe26f5006754#?59034a432fbabe26f5006754=3.2.12-Baseline&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;How often?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I&apos;d say daily, as long as there have been changes since the previous run would be ideal. I&apos;d like the ability to manually trigger if I&apos;m keener as well (as I can do with Evergreen at the moment).&lt;/p&gt;

&lt;p&gt;For non-develop branches I expect it to run rarely, since we only update the content of those branches rarely.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Do we want it automated, or are patch builds sufficient?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I&apos;d like it automated, ideally I won&apos;t need to start patch builds when doing drops from WiredTiger into MongoDB master any more.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Do we want to treat it different than the mainline projects&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I think I&apos;d like it the same, it can probably share the mainline baselines as well.&lt;/p&gt;</comment>
                            <comment id="1567329" author="david.daly" created="Mon, 8 May 2017 21:15:59 +0000"  >&lt;p&gt;Let&apos;s talk about frequency and goals for this. We could enable for sys-perf and or microbenchmarks. It will get a little messy as we will be tracking mongo master and wiredtiger for it, but there&apos;s no reason we can&apos;t do it. &lt;/p&gt;

&lt;p&gt;Questions: &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Which projects?&lt;/li&gt;
	&lt;li&gt;How often?
	&lt;ul&gt;
		&lt;li&gt;Do we want it automated, or are patch builds sufficient?&lt;/li&gt;
		&lt;li&gt;Do we want to treat it different than the mainline projects (possibly because of difference of batch time, or how we want to triage)?&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="505039">SERVER-33647</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>18.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 8 May 2017 14:52:28 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        6 years, 2 weeks, 2 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<s><a href='https://jira.mongodb.org/browse/WRITING-1995'>WRITING-1995</a></s>]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_14262" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>End date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 31 Oct 2017 00:00:00 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>luke.bonanomi@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            6 years, 2 weeks, 2 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alexander.gorrod@mongodb.com</customfieldvalue>
            <customfieldvalue>david.daly@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>ian@mongodb.com</customfieldvalue>
            <customfieldvalue>luke.chen@mongodb.com</customfieldvalue>
            <customfieldvalue>max.hirschhorn@mongodb.com</customfieldvalue>
            <customfieldvalue>michael.cahill@mongodb.com</customfieldvalue>
            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|ht752v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|htdfkn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1978">Storage 2017-12-04</customfieldvalue>
    <customfieldvalue id="2049">Storage 2018-01-01</customfieldvalue>
    <customfieldvalue id="2075">Storage 2018-01-15</customfieldvalue>
    <customfieldvalue id="2094">Storage 2018-01-29</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_14261" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>Start date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 8 May 2017 00:00:00 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hri3a7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>