<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Expectations of a resource monitor set to &quot;Create a build in a release&quot;]]></title><description><![CDATA[<p dir="auto">I'm testing out the git resource monitor feature and had an unexpected (but not shocking) result.  I was testing the scenario of you creating a release it being ready for production but you aren't wanting to to release it just yet but you create a new release to start new work.</p>
<p dir="auto">The resource monitor is set to "Create build in a release" and match "Associated with commit branch".  I was expecting it to look for the first matching release and create the build there (so hoping it would create the build on the newest release).  What ended up happening instead is it created 2 builds, one in each release.</p>
<p dir="auto">I totally understand if this is by design but if it isn't I thought you would want to know.  If it is, I'm curious if there is a way to make it work the way I said.  I don't see it as an unreasonable thing that you will start working on the next release before the previous release is released to production.</p>
<p dir="auto">I'm guessing there is a chance you will say I'd have to go the custom script approach, if that is the case do you have any samples with that?</p>
<p dir="auto">Thank you,<br />
Brandon</p>
]]></description><link>https://forums.inedo.com/topic/5875/expectations-of-a-resource-monitor-set-to-create-a-build-in-a-release</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 02:15:27 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/topic/5875.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 18 Nov 2026 23:50:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Expectations of a resource monitor set to &quot;Create a build in a release&quot; on Thu, 19 Nov 2026 01:37:52 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="/user/brandon_owensby_2976" aria-label="Profile: brandon_owensby_2976">@<bdi>brandon_owensby_2976</bdi></a> ,</p>
<p dir="auto">This is indeed by design. You've got two active releases that are associated with a single branch. So, a commit to that branch will trigger builds in both releases.</p>
<p dir="auto">From a best practices standpoint, you should not start new development work on a branch that is being validated for production. If there's an issue detected during testing, fixing that would involve undoing the new work and/or incorporating even more changes in the pipeline.</p>
<p dir="auto">Your best bet is to not have multiple releases targeting the same branch. If you want to start on a "new release to start new work" while a current release is in the pipeline, I would just create a branch in Git and work off that.</p>
<p dir="auto">Otherwise, I can't think of a work-around here without using some complex/convoluted scripting. There's just no way to programmatically "know" which release the commit was intended for.</p>
<p dir="auto">Hope that helps,</p>
<p dir="auto">Alana</p>
]]></description><link>https://forums.inedo.com/post/20219</link><guid isPermaLink="true">https://forums.inedo.com/post/20219</guid><dc:creator><![CDATA[atripp]]></dc:creator><pubDate>Thu, 19 Nov 2026 01:37:52 GMT</pubDate></item></channel></rss>