Discrepancy between 'Unity Pro Build Server' and 'Professional' license builds

Unity Engine
,
1

My organization’s build process is started via a Bamboo job. The job gathers any repositories configured, pulls them down into a new temp directory, and then checks out specific branches for the build. Once all the source has been pulled down, a manifest.json file is copied from a template and updated to point at the new source folders (rather than artifactory).
The Unity build is performed through the command line using the following flags:

-logfile unity_build.log -projectPath ".\_UnityProject" -executeMethod BuildScript.PerformBuild```

When the Unity build started, I copied all of the source files to my local machine, and ran the same build command. I did have to update the paths because the build server has multiple versions of Unity installed, while I only have the latest version that my organization is using currently (2020.3.6f1).

The result between the two builds was that the server build was missing all text from one of our UIs (all UI were designed in UIBuilder and we are using UIElements 1.0.0.preview-14) Only the UI pieces that are defined in the MainPanel.uxml are missing text, but buttons from that file do work- they will open other windows which all display fine.

My original post regarding this issue, which further details the UI aspects and has a couple side-by-side pictures:
https://discussions.unity.com/t/846150

Once I had a working and non-working build together, I used WinMerge to compare all the binaries. I tracked down the issue to the 'sharedassets0.assets' file.

There is only a 2 byte difference between the files, and it is in an area with references to the UXML elements.
Working build: ```<?n'OverlayWindowPanelu€?ÀBÀB€8?@@@>```
Broken build: ```<?'OverlayWindowPanelu€?ÀBÀB€8?@@@>```
(I've trimmed out extraneous null characters and other whitespace- note the missing "n" at the 3rd character position).

The Build Server consistently produces a broken build, but I have not compared two individual builds side by side to see if it is always broken/corrupt in the same way. What other troubleshooting steps can be taken to determine why the Build server is failing?
2

It turns out that there is some issue when performing a build from the command line on a project which has no Library. The Library gets generated as part of the build, but there is a discrepancy between the contents of the sharedassets0.assets file. The resolution was to perform the command line build twice as part of the build job, to ensure the Library exists at the time of the second build.
I was able to replicate the issue on 4 separate machines by deleting all directories (and their contents) leaving only these three directories:
Assets,
Packages,
ProjectsSettings

After performing a CMD build on each of the 4 machines, they all produced standalone builds with the same issue, and running the CMD build a second time resolved it.