we are running a headless build in our CI/CD pipeline (Azure Devops). 90% of the time, mcuxpresso performs the correct build (e.g. myproject\debug), but for some reason 10% of the time it decides to perform a Clean-only build. We are not asking for a clean-only build, and there is nothing in the build configuration that asks for a clean-only build. It is really interesting in that I can run the exact same command multiple times and mcuxpresso randomly decides upon a clean-only build 10% of the time. Nothing changes between each command execution.
here is the powershell script we are using in the Azure Devops pipeline:
$toolpath = (Resolve-Path "C:\NXP\MCUXpressoIDE*\ide\tools\bin").Path
$exepath = (Resolve-Path "C:\NXP\MCUXpressoIDE*\ide\mcuxpressoidec.exe").Path
$env:PATH += $toolpath
$buildArgs = "-nosplash --launcher.suppressErrors -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data C:\\nxp_workspace -build special_project/Debug"
Start-Process -FilePath $exepath -NoNewWindow -Wait -ArgumentList $buildArgs
Here is the erroneous output (performing clean-only build):
00:13:45 **** Clean-only build of configuration Debug for project dishiq_display ****
make: *** No rule to make target 'clean'. Stop.
"make -r -j12 clean" terminated with exit code 2. Build might be incomplete.
00:13:45 Build Failed. 1 errors, 0 warnings. (took 243ms)
An error has occurred. See the log file
C:\nxp_workspace\.metadata\.log.
