Steam Build Instructions

SimonC4

New Member
Contributor
Here's a quick run down of the steam build process and instructions on how to manually upload a new build should anyone need to do it. The future goal is to setup a dedicated build machine that will be able to automate this process.

Prerequisites
  1. You need to be a Steamworks developer with build permissions on the Destination Sol app.
  2. Download the Steamworks SDK
  3. Run the steamcmd in tools -> Content Builder. The first run downloads and installs some extra files.
  4. Highly recommend reading the documentation: https://partner.steamgames.com/documentation/steampipe
Upload Process
  1. Copy the build scripts from the Destination Sol repo to the steam-sdk directory at: steam-sdk/tools/ContentBuilder/scripts
  2. Get the build you want to use. This is most likely the latest build from Jenkins: http://jenkins.movingblocks.net/job/DestinationSol/
  3. Unzip the file and copy the DestinationSol folder into the steam-sdk directory at: steam-sdk/tools/ContentBuilder/content
  4. Edit the script file app_build_342980.vdf and add a message to the "desc" field. This helps identify the build that you are uploading.
    In most cases you can comment out depots 342982, 342983 and 342984 as these are the JRE for the different operating systems and only need to be included if they have been modified.
  5. From a terminal/command prompt at the ContentBuilder directory, run the following command. Replace username and password with your steam username and password. Change the steamcmd path so it's appropriate for your OS:
    bash ./builder_osx/steamcmd.sh +login username password +run_app_build ../scripts/app_build_342980.vdf +quit
  6. This will upload the files and this will show as a new build in Steamworks under the Builds tab.
Set Beta Live
The next steps depend on what you want to do. The most common approach would be to promote that build to Beta. This is easily achieved by:
  1. Go to the Steamworks Builds tab for the app.
  2. Click the "Select an app branch" in the drop down of the newly uploaded build
  3. Select the Beta branch and click "Preview Change."
  4. Add a comment about the release
  5. Click "Set Build Live Now" to make the build live as the new Beta.
 
Last edited:

Cervator

Org Co-Founder & Project Lead
Contributor
Design
Logistics
SpecOps
Thanks for putting this together :)

Just merged in the scripts and tweaked the remaining outstanding short-term PR. So we could probably put another candidate on Steam and get it beta tested.
 

SimonC4

New Member
Contributor
The documentation said that there was an extra step for releasing on Mac so that file permissions are kept. However, I didn't do that and it hasn't seemed to have caused any issues.

I've done a small update to point #4 in the upload process. The depots that only contain the JRE don't need to be included in each upload as they'll automatically get included from the previous version.
 
Top