@@ -52,19 +52,28 @@ The MobSF template uses some global configuration used throughout all jobs.
Only one of the `mobsf-app-scan` and `mobsf-app-scan-service` jobs is launched depending on whenever the `MOBSF_CLIENT_IMAGE` and `MOBSF_API_KEY` are set.
### `mobsf-on-server` job
### `mobsf-pkg-xxx` jobs
It uploads the packaged mobile application (APK or IPA) to the MobSF server described by variables, requests a scan and gets the report.
Depending on whether the `server-url` / `MOBSF_SERVER_URL` configuration is set or not,
the template will run a scan of your application package (APK or IPA), either locally (`mobsf-pkg-local` job) or remotely (`mobsf-pkg-remote` job).
It is bound to the `package-test` stage.
Both use the [official Docker image](https://hub.docker.com/r/opensecurity/mobile-security-framework-mobsf/), and are bound to the `package-test` stage.
### `mobsf-code` Job
### `mobsf-local` job
This job performs static analysis of the application's source code using the [mobsfscan](https://github.com/MobSF/mobsfscan) tool.
It runs a scan on a local MobSF server using the [official Docker image](https://hub.docker.com/r/opensecurity/mobile-security-framework-mobsf/).
It has the following variables:
It is bound to the `package-test` stage.
| Input / Variable | Description | Default value |