Tracking Experimentanl Changes - Rust

Is there a way to track what changes get pushed into a new Steam build? Also, am I under the correct assumption the experimental branch (found in the beta section of Steam) for the client gets updated on a very similar biases to the dedicated experimental branch? Been tracking these via steamdb, it appears to be similar but I'd like confirmation. I'm aware there is a twitter bot that monitors the Facepunch SCM, however I'm not always certain how often a build created, then pushed to Steam.

Commit -> [URL="https://twitter.com/RustUpdates"]Twitter Update[/URL] -> [URL="http://jenkins.facepunchstudios.com/view/Facepunch/"]Build & Upload [/URL] -> Experimental Branch -> Default Branch, manual (periodically, 1-3 times a day)

[QUOTE=garry;45600894]Commit -> [URL="https://twitter.com/RustUpdates"]Twitter Update[/URL] -> [URL="http://jenkins.facepunchstudios.com/view/Facepunch/"]Build & Upload [/URL] -> Experimental Branch -> Default Branch, manual (periodically, 1-3 times a day)[/QUOTE] garry, have you found a fix for the cert errors yet? The issue remains in the current server.

[QUOTE=garry;45600894]Experimental Branch -> Default Branch, manual (periodically, 1-3 times a day)[/QUOTE] I'm a bit confused about the experimental server branch. is it correct that the normal Rust legacy has the "default" experimental branch and then there's the beta experimental branch that gets all the builds, and the experimental server gets the beta experimental branch updates? So does that mean it's possible to have servers newer than the clients in the default experimental branch? will they work together? edit: for server updates I use [url]http://steamdb.info/app/258550/history/[/url], although they don't really "track" anything. sorry for being off topic a little.

[QUOTE=Gachl;45601665]I'm a bit confused about the experimental server branch. is it correct that the normal Rust legacy has the "default" experimental branch and then there's the beta experimental branch that gets all the builds, and the experimental server gets the beta experimental branch updates? So does that mean it's possible to have servers newer than the clients in the default experimental branch? will they work together? edit: for server updates I use [url]http://steamdb.info/app/258550/history/[/url], although they don't really "track" anything. sorry for being off topic a little.[/QUOTE] Garry, please correct me if I'm wrong, but this is my understanding: The client beta experimental branch gets update pushes immediately on build and upload. Default experimental gets pushes manually. This lets the beta experimental be the hot build with the potential to make the game explode in flames on startup without ruining everyone's experimental client until the bug gets fixed. No idea how the server updating is handled, and I know that's your question, but I imagine the server could accept ranges of builds up to the last 'stock' experimental branch update without returning the out-of-date client response.

I'm also a bit "confused" on how the experimental server and the client (this also includes legacy) are being kept "in sync". Technically these are two different Steam App IDs. Please correct me if I'm wrong, but from what garry posted earlier it would appear to me both experimental branches for the client and server are automatically uploaded once a change is committed (and it builds successfully). However the default branch for the client is manually pushed.

It works like this The code is built and uploaded to Steam. Which makes it live on the experimental beta branch. Periodically during the day, usually when there's a protocol change, we set the default branch to same version as the experimental branch, so that people who haven't opted in can still join servers.