We are currently extensively using the Unity3d-Plugin for all kinds of builds, from nightly dev-builds to random normal builds and it works like a charm. The only issue we currently have, is that the unity build steps are really static. If you need to launch Unity with a different commandline argument in the middle of your build process, you need to duplicate a lot of previous steps to get the desired result.

We for instance have two build tasks which launch our build process. One causes the build to be a dev build where the profiler can be attached and the other one is a normal build without the Dev build flag. Both start in the same way, first an SVN update, then some small changes to some files and then a unity build step which is different in both tasks. After that both build tasks trigger the same build as the following build steps are the same for both processes.

If we now change some things in the first area, it causes an overhead as we need to change the same thing twice. In our case right now its not a really huge issue, because it only happenes once at the beginnig of our process. But if you need to launch Unity on several different occasions troughout the process with different parameters to, the complexity and overhead increases exponetially.

Now to my idea on how to reduce the overhead:
A build taks can be launched parametrized which allows you to define environment variables. If those are queried in the plugin an if else structure could be created.

e.g. The build process has 2 parameters A and B.
if (A = X)
launch unity with parameters A
else
if (B = Y)
launch unity with parameters B
else
launch unity with parameters C

This would merge all mostly duplicate build branches back into one continuous flow and everything could be defined at the start of the build either manually or with the default parameter settings, which makes it way easier to maintain and to keep the overview over the build process.

It would be really cool if this feature is at some point in the plugin.
Thanks in advance and keep up the good work.

Best regards,
Manuel Matscher