GameCI 6: Conclusion

GameCI 6: Conclusion

Continuing from GameCI 5, let’s finish by examining the Deploy to the Steam Marketplace and Announce Release to Social Media jobs.

Deploy to the Steam Marketplace

  deployToSteam:
    name: Deploy to the Steam Marketplace
    runs-on: ubuntu-latest
    needs:  buildWithWindows
    if: github.event.action == 'published' || (contains(github.event.inputs.workflow_mode, 'release') && contains(github.event.inputs.workflow_mode, 'Steam'))
    steps:
      - name: Checkout Repository
        uses: actions/checkout@v3
      - name: Download StandaloneWindows Artifact
        uses: actions/download-artifact@v3
        with:
          name: cgs-StandaloneWindows
          path: build/StandaloneWindows
      - name: Download StandaloneLinux64 Artifact
        uses: actions/download-artifact@v3
        with:
          name: cgs-StandaloneLinux64
          path: build/StandaloneLinux64
      - name: Download StandaloneWindows64 Artifact
        uses: actions/download-artifact@v3
        with:
          name: cgs-StandaloneWindows64
          path: build/StandaloneWindows64
      - name: Download App
        uses: actions/download-artifact@v3
        with:
          name: Card Game Simulator.app
          path: build/StandaloneOSX/Card Game Simulator.app
      - name: Deploy to Steam
        uses: game-ci/steam-deploy@v1
        with:
          username: ${{ secrets.STEAM_USERNAME }}
          password:  ${{ secrets.STEAM_PASSWORD }}
          configVdf: ${{ secrets.STEAM_CONFIG_VDF }}
          ssfnFileName: ${{ secrets.STEAM_SSFN_FILE_NAME }}
          ssfnFileContents: ${{ secrets.STEAM_SSFN_FILE_CONTENTS }}
          appId: 1742850
          buildDescription: v${{ needs.buildWithWindows.outputs.buildVersion }}
          rootPath: build
          depot1Path: StandaloneWindows
          depot2Path: StandaloneLinux64
          depot3Path: StandaloneWindows64
          depot4Path: StandaloneOSX
          releaseBranch: prerelease

You can’t call yourself a Game Developer unless you have a game published on Steam, right?

Well, that statement may be going too far, but it’s undeniable that Steam is a huge force in gaming.

As such, having automated Steam deployments is likely going to be desirable for a lot of game developers. And for that, refer to the GameCI Steam deployment docs.

Note 2 additional details:

1. This job only runs when triggered by either a GitHub Release or a workflow dispatch with release Steam as the input.
2. You’ll still need a small/quick manual step to promote the prerelease branch to the default branch in the SteamWorks dashboard.

Announce Release to Social Media

  announceReleaseToSocialMedia:
    name: Announce Release to Social Media
    runs-on: ubuntu-latest
    needs: [buildWithWindows, deployToAppStore, deployToGooglePlay, deployToGitHubPages, deployToMacAppStore, deployToMicrosoftStore, deployToSteam]
    if: github.event.action == 'published'
    steps:
      - name: Checkout Repository
        uses: actions/checkout@v3
      - name: Prepare Announcement
        id: prepare
        shell: bash
        env:
          VERSION: v${{ needs.buildWithWindows.outputs.buildVersion }}
          RELEASE_NOTES: ${{ github.event.release.body }}
        run: |
          export ANNOUNCEMENT="Released CGS $VERSION! $RELEASE_NOTES"
          ANNOUNCEMENT="${ANNOUNCEMENT//'%'/'%25'}"
          ANNOUNCEMENT="${ANNOUNCEMENT//$'\n'/'%0A'}"
          ANNOUNCEMENT="${ANNOUNCEMENT//$'\r'/'%0D'}"
          echo "$ANNOUNCEMENT"
          echo "::set-output name=ANNOUNCEMENT::$ANNOUNCEMENT"
      - name: Discord Announcement
        env:
          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
        uses: Ilshidur/action-discord@0.3.2
        with:
          args: ${{ steps.prepare.outputs.ANNOUNCEMENT }}
      - name: Twitter Announcement
        uses: ethomson/send-tweet-action@v1
        with:
          status: ${{ steps.prepare.outputs.ANNOUNCEMENT }}
          consumer-key: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
          consumer-secret: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
          access-token: ${{ secrets.TWITTER_ACCESS_TOKEN }}
          access-token-secret: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}

This last job is short and sweet.

It creates some announcement text that looks like Released CGS $VERSION! $RELEASE_NOTES. It does some processing to allow new lines in that text. And then it uses the Ilshidur/action-discord and ethomson/send-tweet-action actions to post on Discord and make a Tweet.

After all, we gotta let the world know everything about our app.

Final Thoughts

Speaking of letting the world know about our app, you likely noticed Card Game Simulator (CGS) come up in this series. If you’re interested in being able to create, share, and play card games online, please check out the CGS website!

With the necessary self-promotion done, I also need to mention that I hope this series has been helpful! If you have additional questions or if you just want to talk, please join us on the GameCI Discord Server!