Managing files on Bitrise allows you to upload files to use in your builds. You are required to upload files for the purposes of code signing. Builds also produce files as outputs. The good news is that this is all very simple!
Uploading files to use in your build ⚓
If your build requires any files to make it work, upload them to the Generic File Storage. The Generic File Storage accepts any file type, all you need to do is provide a unique ID and upload the file.
- Go to the Dashboard.
- Open the app you want to add files to.
- Open the Workflow Editor.
Click the Code Signing tab.
Scroll down to the Generic File Storage and provide a unique ID to your file.
The unique ID will be part of the generated download URL that Bitrise stores as an Environment Variable.
Upload the file by clicking Upload file.
Remember that the file size cannot exceed 5 MB.
Now you can use this file in a variety of ways in your build - read more in the detailed guide about the Generic File Storage.
Once a file is uploaded, it can also be:
- Downloaded by anyone who has Admin or Owner role on the app’s team on Bitrise, unless it is protected.
- Exposed to pull request builds.
Code signing files ⚓
Bitrise can do your code signing for you but we need some files to make it happen.
For Android apps, upload code signing files to the Generic File Storage.
For iOS files, you need to use the dedicated menu options for provisioning profiles and code signing identities.
Output files ⚓
Builds can generate and export files: for example, you can export a binary package file of your app with a Bitrise build. You can easily find these files:
- Open the build that you ran.
- Go to the Apps & Artifacts tab.
- View and download the generated files.
You can read more about build artifacts in our detailed guide!
Using encrypted files ⚓
You can use encrypted files on Bitrise, easily and securely. All you need to do is encrypt the file on your computer, upload it to your repo and use a Step to decrypt it when you need it.
In this example, we’ll show how to do this. We use the pwgen password generator tool and GPG as the encryption software.
- Open your Terminal/Command Line.
Create a 32 character passphrase for encryption.
pwgen -s 32 1
Encrypt your file.
gpg -c my_secret_file
Optionally, you can encrypt your file(s) in a non-interactive way.
gpg --batch --passphrase <passphrase> -c my_secret_file
my_secret_fileto the Generic File Storage on Bitrise.
- Add the Decrypt file Step to your workflow.
- Add your passphrase as a secret Environment Variable and insert it to the relevant Step input.
Add the encrypted file path and the output file path to the relevant Step inputs.
You can find the Environment Variable for the encrypted file path in the Generic File Storage.
That’s it! Once you run the build, the Step will decrypt your file and you can use it for whatever you need it for!
If you add the Deploy to bitrise.io step to your workflow, once the build has run, you can access the build’s artifacts in the APPS & ARTIFACTS tab. You can...