borgogelli

Now, we need to sign the unsigned APK and run an alignment utility on it to optimize it and prepare it for the app store. If you already have a signing key, skip these steps and use that one instead.

Let’s create keystore file using this command Syntax:

keytool -genkey -v -keystore .keystore -alias -keyalg -keysize -validity

For Example :

borgogelli

#!/usr/bin/env bash
#
# Install required dependencies with android command
#

for DEP in android-25 \
         build-tools-25.0.2  \
         tool \
         extra-android-m2repository \
         extra-android-support \

borgogelli

# create keystore file
keytool -genkey -v -keystore [my-release-key].ketstore -keyalg RSA -validity 1000 -alias [some_alias]
# sign package
jarsigner -keystore my-release-key.ketstore [some-release-unsigned.apk] some_alias
# verify signed package
jarsigner -verify [some-release-unsigned.apk]

borgogelli

Simple Git Workflow For Continuous Delivery

Workflow guidelines:

• master branch is always production-ready, deployable, 100% green test suite
• New development is done on feature branches, with frequent rebasing onto master
• Clean commit history by preferring to rebase instead of merge (git pull is configured to automatically rebase)

Workflow

borgogelli

Default

Powerlevel9k

borgogelli

#!/usr/bin/env bash
#
# Install JUST the required dependencies for the project.
# May be used for ci or other team members.
#

for I in android-25 \
         build-tools-25.0.2  \
         tool \
         extra-android-m2repository \

borgogelli

# Extracted from https://stackoverflow.com/questions/7244321/how-do-i-update-a-github-forked-repository

# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches,
# such as upstream/master:

git fetch upstream