Is it possible to register a serial via the command line without actually running a build?
I have set up a system where we are able to "share" a couple of license keys across a number of Jenkins build agents by using the unity.exe -serial command line switches before using the Unity3d Builder plugin to do the actual build, then calling Unity.exe -returnLicense when it's all done to return the activation to the "pool".
What i'm observing though, is that immediately after successfully obtaining the .ulf license key file, that execution of unity then goes on and tries to compile the unity project that was last compiled on that Jenkins slave. But, since i'm not sending in the -executeMethod nor any of the -build* parameters at that time, I would expect that execution of unity.exe to ONLY try to grab a license for the serial number provided and exit with feedback on whether or not it succeeded.
Is there a way to make unity.exe NOT try to compile the most recently compiled project when trying to obtain or return a license key via the command line, using the -serial or -returnLicense switches?
Eventually, we will probably have multiple projects using Unity, and quite possibly sharing the same build infrastructure. Having Unity try to build projects that may or may not exist on that node at any given time will be problematic if it errors out and kills my build due to that bogus situation.
After some consideration, it really strikes me that Unity, especially in -batchmode, should not try to build anything unless it's explicitly given a project to build.
So, with that in $$anonymous$$d, I added -createProject "c:\temp" to the end of my calls to register and return the serial, and ins$$anonymous$$d of trying to build my whole project, it just creates this super small, empty project and exits quickly, without any fuss.