Hosted build pipeline fails where non hosted is successful

(5) Share

Report

Posted on by Jan M.

3,315

On a hosted build pipeline there is an error, class does not have CoC, but the source has it. The same code with another pipeline based on a VM runs successful.

The hosted one runs with Agent version 4.264.2 the other with 4.258.1. Can that be a reason?

Thanks for help.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Martin Dráb 239,647 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Moved from Integration, Dataverse, and general topics forum to Finance | Project Operations, Human Resources, AX, GP, SL forum - the mention of CoC suggests that the question is about F&O.

Please mention the version of F&O in both cases, not the agent version.

Also, please tell us more about the error.

Was this reply helpful? Yes No
CU26110852-0 2 on at

Like (0)

Report
Copy link

Link copied!

Yes, the difference in the Azure DevOps Agent version could potentially be the reason for the discrepancy, especially when dealing with Code of Conduct (CoC) errors in a build pipeline. Newer agent versions (like 4.264.2 in the hosted environment) sometimes include updates, patches, or changes in how they interact with build tools, dependencies, or security policies, which might expose an underlying issue in the build process or the environment setup that the older agent version (4.258.1) was inadvertently masking or handling differently.

Was this reply helpful? Yes No
Sagar121 1,187 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Could you please confirm if “Hosted pipelines” means you are using Microsoft-hosted agents, and “VM pipelines” means you have set up your own agent on a virtual machine?

If that’s correct, then you’ll definitely need to update the NuGet packages to VM build agent version matches the version.

Was this reply helpful? Yes No
Martin Dráb 239,647 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@CU26110852-0 It doesn't make sense. For example, what are Code of Conduct (CoC) errors in a build pipeline? CoC actually means Chain of Command. If you used AI to generate the answer, note that just blindly posting anything what AI made up isn't a legitimate use of this forum. Please refer to Responsible AI policies for the Community to learn how to use it correctly.

Was this reply helpful? Yes No
Jan M. 3,315 on at

Like (0)

Report
Copy link

Link copied!

@CU26110852-0 @Sagar121 yes, can confirm the setup as you described

@Martin Dráb right, why the agent version should now handle CoC that different?

Error: ##[debug]Processed: ##vso[task.logissue type=Error;sourcepath=D:\a\8\NuGets\Microsoft.Dynamics.AX.Platform.CompilerPackage\DevAlm\Microsoft.Dynamics.Framework.Tools.BuildTasks.17.0.targets;linenumber=85;columnnumber=5;code=;]Error: SKS_LB_SecondaryMatch_TASCustomONAG_Extension/forceRemittanceRuleCheck(12,9) - No chain of command next method found in method 'forceRemittanceRuleCheck' of class 'SKS_LB_SecondaryMatch_TASCustomONAG_Extension'. The model being extended may be out of date, please recompile the model containing the element being extended.

<?xml version="1.0" encoding="utf-8"?>

<AxClass xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

<Name>SKS_LB_SecondaryMatch_TASCustomONAG_Extension</Name>

<SourceCode>

<Declaration><![CDATA[

[ExtensionOf(classStr(SKS_LB_SecondaryMatch))]

public final class SKS_LB_SecondaryMatch_TASCustomONAG_Extension

{

}

]]></Declaration>

<Methods>

<Method>

<Name>forceRemittanceRuleCheck</Name>

<Source><![CDATA[

public boolean forceRemittanceRuleCheck()

{

next forceRemittanceRuleCheck();

return true;

}

]]></Source>

</Method>

</Methods>

</SourceCode>

</AxClass>

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,647 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Q: why the agent version should now handle CoC that different?

It's not about the build agent. The agent is just infrastructure doing things like running tasks and collecting output message. The compilation is done by X++ compiler and the result depends on the compiler itself, its parameters and input files, especially files with X++ code. You need to pay attention to version of F&O files, not the build agent version.

I see you're extending a class that isn't a part of the standard application; it seems to be an ISV solution. You're trying to extend forceRemittanceRuleCheck(), but the compiler suggests that no such a method exists in SKS_LB_SecondaryMatch class. This likely means that you wrote the code against a different version of the ISV solution than what you're using during the build. Check these versions.

1 people found this reply helpful.

Was this reply helpful? Yes No
Jan M. 3,315 on at

Like (0)

Report
Copy link

Link copied!

The ISV does have the method in source and is compiled first. But I see also the bin is checked in with an older version.

So the VM will compile and replace the dll, what will be the actual version.

Thank you Martin.

Was this reply helpful? Yes No