https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-17064 Lustre <p>It would be useful to allow Jenkins to do very limited builds for fortestonly patches with directories in the patch commit message.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Build-Parameters: clientdistro=el7.9 Test-Parameters: fortestonly clientdistro=el7.9 serverversion=2.15.3 </pre> </div></div> <p>Since it isn't possible to do this (it will always start all of the builds) it seems possible to have lbuild check the directives in the commit message and just "<tt>exit 0</tt>" at the start of the build without actually building anything. </p> <p>This would also be useful for cases of patches which are based on an old parent (eg. to give an old build to a customer) that currently fail if the build support for a distro is not in the old code being built and fails the build instead of building for the available distros:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>17:19:09 + error 'Target 4.18-rhel8.8 was not found.' 17:19:09 + local 'msg=Target 4.18-rhel8.8 was not found.' </pre> </div></div> LU-17064

Allow limited builds

Improvement Minor Open Unresolved WC Triage Andreas Dilger Thu, 31 Aug 2023 01:23:40 +0000 Thu, 5 Oct 2023 07:59:01 +0000 0 4 <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=mdiep" class="user-hover" rel="mdiep">mdiep</a>, as a starting point, I was thinking of replacing the "<tt>fatal 1 "Target $TARGET was not found."</tt>" and "<tt>fatal 1 "${LBUILD_DIR}/lbuild-$DISTROMAJ not found"</tt>" cases in <tt>lbuild</tt> with just an error message and "<tt>exit 0</tt>"? That would allow builds to finish without error when built on an old branch that doesn't have newer distro support, at the risk of not building some packages in rare cases. I think that is pretty unlikely and we would notice it as soon as testing could not be run?</p> <p>I couldn't see where the <tt>lbuild</tt> script had access to the Lustre sources, unless it is run in the Git tree itself? Then I could just use "<tt>git log -1</tt>" to get the commit message and look for <tt>Build-Parameters:</tt> lines in the output?</p> <p>"Andreas Dilger &lt;adilger@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/52448" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/52448</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-17064" title="Allow limited builds" class="issue-link" data-issue-key="LU-17064">LU-17064</a> build: check for Build-Parameters in commit<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 1b4046f20c27794ba6915fc880440a9b27f34aa0</p> <p>@minh, one strange thing I noticed with my patch is that it seems the ubuntu2204 builder is not using the lbuild script from the current tree, but a separate one? It is always doing a full build and not printing any debug messages from the patch...</p> <p>Right, for ubuntu* it's just simply make debs</p> <p>But it still looks like the Ubuntu2204 build is running some variant "<tt>lbuild</tt>", but an old version of the script that is not the one from the build tree since there is no "<tt>lbuild-ubuntu2204</tt>" or similar version in the tree at all.</p> <p>Charlie, Minh thought that this functionality would be better to implement directly in the Jenkins Groovy scripting, like ATM-2884 because it would allow the non-builds to skip the queue entirely, rather than waiting in the queue and assigned a builder just to find that nothing is needed.</p> <p>Ideally, this would also allow a "trivial" keyword to allow building specifically the distro/arch that is used for <tt>Test-Parameters: trivial</tt> testing.</p> <p>The main goal here is to reduce the build and test time for patch series of 20 or 30 patches that contain a series of <em>actually</em> trivial changes like code movement and variable renaming.</p> Related Development Rank 1|i03u9r: Rank (Obsolete) 9223372036854775807 Severity