The idea to upload those build artifacts to sf.net is really an afterthought, we originally just need to have CI test. There is no canonical way to configure Urho3D build tree. We have our own technical constraint and reasoning when choosing those build options for CI build. Take LuaJIT build option for example, we can only enable it whenever it is supported by the compiler toolchain provided by our CI server and unfortunately MinGW CI build on Travis CI server was found to be incapable to handle LuaJIT building. Travis VM is (still) running on the ancient Ubuntu 12.04 LTS operating system. You are better off building the Urho3D library yourself from source. Having said that, we do have Windows/DX11 build with LuaJIT enabled using MSVC compiler in AppVeyor (another CI server running on Windows Server).
I think it is a design decision. We could have provided an option to build the 3rd-party libraries as SHARED library, however, we don't provide one and instead always build them as STATIC and to be linked internally by Urho3D library. This is because in quite a number of cases we have made local patches to those 3rd-party libraries either for quick bug fixes or to change it to suit our own need. So even if we could build them as SHARED libraries, it was not really safe to replace them with other (presumably newer) version from outside of Urho3D build tree.