Differences between SSRS 2016 and Report Builder 2016

With RB (and sufficient privilege), users can save reports straight to the Report Manager environment. At that point, they're deployed. But if you want to have them save those reports to a Dev/Test box, and want to push them live, there's a few options.

One easy option is to move reports into a known folder 'For Deployment'. You can then have a script which grabs the RDL for reports in here and uploads them to the proper server. You'll probably want to make sure the data sources are mapped appropriately as this method can annoyingly lose references. You can use rs.exe for your scripts, or just use the web references. PowerShell can be very useful here, as it happily talks WebService, and you can schedule PowerShell scripts using SQL Agent jobs.

Depending on the version of Report Builder, you can only build from a single data source. I'm pretty sure this is still the case with SQL Server 2008R2, although Report Builder 3 can consume data directly from a database without needing a report model, although you need to build data sets using the individual connections and I don't think you can group items from different data sets by a common value.

You can do this gouping with SSRS (see this article for an overview), although I can't see an obvious way to do it in RB3. This article indicates that you can't nest items based on different data sets, so it's looking like common rollups aren't possible in RB3.