lisawray/groupie

Automate library releases

Open

#315 opened on Nov 28, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (3,627 stars) (295 forks)batch import
enhancementhelp wanted

Description

Currently there is a manual process related to releasing a Groupie version. I'd like to automate that using the CircleCI setup we already have in place.

Basically, I want any tagged commits to automatically create a new release.

I have the keystore file and it's details and I can add them as encrypted files + variables to whatever CircleCI setup is made.

If anyone has CircleCI experience I'll welcome PRs or guides to do this.

Contributor guide

Tech stack
java
Domain
ci cdrelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
CircleCI experienceAndroid release knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
The issue requests automating releases using CircleCI. The maintainer has a keystore file and can provide encrypted variables. A PR should add a CircleCI config (e.g., .circleci/config.yml) that triggers on tags to build and publish the library. The existing CircleCI setup should be leveraged. No specific code changes are needed beyond CI configuration. Look at current CircleCI config if any, and ensure secure handling of signing keys.