nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Generate Signed APK using Bitbucket pipeline

Manish Kumar_a7r4zd

Hi everyone,

I am trying to build release-signed apk using bitbucket pipeline. I am able to make release build but not sure how to sign it using BB pipeline. I have following queries here

1. Where to store .keystore file for signing

2. How to use it in bitbucket-pipeline.yaml file

Accepted answers

Manish Kumar_a7r4zd

Hi everyone,

Just answering my own question

1. Encode keystore file into base 64 (can use terminal to do same)

base64 > keystore_file

2. Create a secure repo variable and store the base64 value

3. Decode keystore file during build process

echo "$SIGNING_JKS_FILE" | base64 -d > keystore_file

Since this is secure variable it will not be printed anywhere

4. Now we can go ahead with our normal build process.

All comments

Manish Kumar_a7r4zd

Hi everyone,

Just answering my own question

1. Encode keystore file into base 64 (can use terminal to do same)

base64 > keystore_file

2. Create a secure repo variable and store the base64 value

3. Decode keystore file during build process

echo "$SIGNING_JKS_FILE" | base64 -d > keystore_file

Since this is secure variable it will not be printed anywhere

4. Now we can go ahead with our normal build process.

Keshava11

Hi @Manish Kumar do we not required to give any keystore passwords , keystore aliases etc. ?

Will it create a signed apk without it

Keshava11

1. Encode keystore file into base 64 (can use terminal to do same)

base64 > keystore_file

What is the exact command ?
This just hangs

Manish Kumar_a7r4zd

Hi @Keshava11

You need to create secure repo variable for all credentials like KEYS_STORE_ALIAS, KEY_STORE_PASSWORD etc. and utilise these environment variable during signing. Since it's secured repo variable it will not be disclosed.

harrie

Store keystore in Bitbucket secured storage set passwords and alias as repository variables and copy keystore in pipeline so Gradle can sign the APK

Kassy Shane

You can store the keystore as a Base64 string in repository variables and decode it in the pipeline. First convert the keystore locally using the base64 command and save the output in a text file. Copy that content and store it as a secured variable like KEYSTORE_BASE64. In the pipeline script decode it back into a file and run the Gradle release build. Add the alias and passwords as secured variables and reference them in gradle properties. This way the pipeline can sign the APK without committing the keystore to the repository.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines

android