Should we include the following files in the UCB-targeted repository?

I'm wondering about two sets of files I always exclude from my Unity project repositories:

1. Assembly/solution files (sln, csproj and such). Until recently I had no trouble excluding them from the repository, but I just had a build fail after removing Vuforia plugins from my project, with the log suggesting that UCB was using an assembly file still referencing those plugins. Can someone clarify whether UCB attempts to generate those files by itself on every single pull (my error suggests otherwise), or whether it actually expects them to be present in the repository?

2. Library files. I had no trouble with UCB builds excluding them from repository, and I'm very hesistant to include them, as, as you can imagine, they will clutter commit history and repo size quite a bit. I'm also aware that UCB can generate them by itself and persists those files between builds. But I'm wondering whether including library files in the files for the very first UCB build can allow UCB to skip all import tasks, therefore dropping hours from build time (in particular, as you well know, PVRTC compression for iOS target is incredibly slow). After that first build, thinking follows, you remove all Library files from the repo, they remain persisted in UCB as per project settings, and you only deal with added time from modified assets. Can someone clarify whether such an approach to speeding up the first build is possible, or whether UCB always ignores the Library folder arriving from the repo?

 

Ah, alright, that's great to hear!

I think I figured the issue with removed plugins causing a build error - I missed a stray link file, so the it wasn't caused by assembly files being outdated.