Skip to content

Figure out how to make signing release builds easier for developers #44

@mcomella

Description

@mcomella

Post GA?

Why/User Benefit/User Problem

In order to use "release" build variants like forPerformanceTest, we have to do our own signing. However, it's non-trivial integrate release signing into the regular Android Studio build process: this bug is to make it easy.

Impact

Without this, setting up local performance builds is an annoyance: developers have to do something hacky like adding local signing configurations and remember not to check them into the tree.

Acceptance Criteria (how do I know when I’m done?)

  • It is easy for developers to create signed forPerformanceTest builds
  • Documentation (e.g. in README) is updated
  • Folks are notified of any changes to their workflow

Solution ideas:

  • We check a debug.keystore into the tree that signs forPerformanceTest builds and provide a signing config for it
  • Developers can specify a path to their debug.keystore and it will integrate the signing
  • Developers add custom run configs with signing in AS

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions