-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Description
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
forPerformanceTestbuilds - 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
forPerformanceTestbuilds 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