Command Line Usage – CI/CD Pipelines
The GameBench Performance Injector can also be controlled via the command line, making it ideal for integration into CI/CD pipelines and automated testing workflows. In this mode, the standard app window does not open, and the process exits automatically once the task is complete.
The syntax is:
Mac: /Applications/GameBench\ Injector.app/Contents/MacOS/GBPerfInj [OPTIONS] INPUT_BUNDLE
Windows: %AppData%/Local/gbtoolgui/GBPerfInj.exe [OPTIONS] INPUT_BUNDLE
Where INPUT_BUNDLE is the path to your input .apk/.app/.ipa/etc, and [OPTIONS] is zero or more options from this list:
| Option | Notes |
|---|---|
| GameBench server | |
--server |
Defaults to https://web.gamebench.net/ |
--user |
|
--apiToken |
Obtainable from https://web.gamebench.net/manage/user/me/api-tokens |
--pasword |
Use if not using –apiToken |
--sso |
true or false (default) |
| Google Identity-Aware Proxy (IAP) | |
--iapServiceFile |
|
--iapClientId |
|
| Android code-signing | |
--keystorePath |
|
--keystorePassword |
|
| iOS code-signing | |
--appleId |
|
--localCodeSigningAssets |
One or more code signing asset file paths (as separate args) |
| Injection Options | |
--screenshotInterval |
Defaults to 10 seconds |
--verboseLog |
true or false (default) |
--disableOverlays |
true or false (default) |
--injectType |
normal (default) or inject or sign |
Last updated on