# Codemagic CLI tools > How to use Codemagic CLI tools locally or in other environments [codemagic-cli-tools](https://pypi.org/project/codemagic-cli-tools/) is a set of tools to simplify builds at Codemagic. They can be installed with via pip and run locally. ```bash pip3 install codemagic-cli-tools ``` For more information, review the full documentation on [CLI tools](https://github.com/codemagic-ci-cd/cli-tools/tree/master/docs#cli-tools). > > **Note:** Requires: Python ≥ 3.8 > ## Build and code sign an Xcode project To fetch (or create and download) the provisioning profile(s) and certificate for `MY_BUNDLE_ID` app, use the [app-store-connect](https://github.com/codemagic-ci-cd/cli-tools/blob/master/docs/app-store-connect/README.md#app-store-connect) tool. ```bash app-store-connect fetch-signing-files \ --issuer-id ISSUER_ID \ --key-id KEY_IDENTIFIER \ --private-key PRIVATE_KEY \ --certificate-key PRIVATE_KEY \ MY_BUNDLE_ID ``` By default, your certificate will be saved to `$HOME/Library/MobileDevice/Certificates` and the provisioning profile(s) will be saved to `$HOME/Library/MobileDevice/Provisioning Profiles`. Refer to [Signing iOS apps](../code-signing-yaml/signing-ios/) for more information about accessing App Store Connect. To initialize keychain at system default keychain path with empty keychain password and add your `certificate.p12` with certificate password, use the [keychain](https://github.com/codemagic-ci-cd/cli-tools/blob/master/docs/keychain/README.md#keychain) tool with the following command: ```bash keychain initialize keychain add-certificates --certificate /path/to/certificate.p12 --certificate-password CERTIFICATE_PASSWORD ``` Note that `--certificate` option can be either a path literal, or a glob pattern to match certificates. To use the provisioning profile from `/path/to/profile.mobileprovision` in your Xcode project located at `/path/to/MyProject.xcodeproj` and generate an .ipa archive using scheme `MyScheme`, use [xcode-project](https://github.com/codemagic-ci-cd/cli-tools/blob/master/docs/xcode-project/README.md#xcode-project) with the following command: ```bash xcode-project use-profiles --project /path/to/MyProject.xcodeproj --profile /path/to/profile.mobileprovision xcode-project build-ipa --project /path/to/MyProject.xcodeproj --scheme MyScheme ``` Note that `--project` option can be either a path literal, or a glob pattern to match projects in the working directory (default is `**/*.xcodeproj`). `--profile` option can be a glob pattern as well (default is `$HOME/Library/MobileDevice/Provisioning Profiles/*.mobileprovision`). ## Generate universal .apk(s) with user-specified keys from the app bundle To build .apk files(s) from the app bundle(s) found with `/path/to/**/*.aab` glob pattern with keystore `/path/to/keystore.keystore`, `KEYSTORE_PASSWORD`, `KEY_ALIAS` and `KEY_PASSWORD`, use the [android-app-bundle](https://github.com/codemagic-ci-cd/cli-tools/tree/master/docs/android-app-bundle#android-app-bundle) tool: ```bash android-app-bundle build-universal-apk \ --bundle '/path/to/**/*.aab' \ --ks /path/to/keystore.keystore \ --ks-pass KEYSTORE_PASSWORD \ --ks-key-alias KEY_ALIAS \ --key-pass KEY_PASSWORD ``` If `--bundle` option is not specified, default glob pattern `**/*.aab` will be used. Please make sure to wrap the pattern in single quotes. > > **Tip:** Instead of entering `ISSUER_ID`, `KEY_IDENTIFIER`, `PRIVATE_KEY`, `CERTIFICATE_PASSWORD`, `KEYSTORE_PASSWORD`, `KEY_PASSWORD` as plaintext, you may specify them using an `@env:` prefix followed by an environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:` uses the value in the environment variable named ``, and `@file:` uses the value from file at ``. > > Please refer to the [documentation](https://github.com/codemagic-ci-cd/cli-tools/tree/master/docs#cli-tools) for more details. > ## Generate a changelog text from Git history To generate a changelog text from Git history, use the [git-changelog](https://github.com/codemagic-ci-cd/cli-tools/tree/master/docs/git-changelog#git-changelog) tool. For example, to generate a changelog to `CHANGELOG` file starting from the previous tag, use: ```bash git-changelog generate --previous-commit ${CM_PREVIOUS_COMMIT} \ `git rev-list --tags --skip=1 --max-count=1` > CHANGELOG ```