Opened 2 years ago

Closed 11 months ago

#5871 closed change (rejected)

Auto-deploy to Play Store

Reported by: jwangenheim Assignee:
Priority: Unknown Milestone:
Module: Adblock-Plus-for-Samsung-Browser Keywords:
Cc: diegocarloslima, mario, fhd Blocked By:
Blocking: Platform: Android
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description

Background

We already use Circle CI for continuous integration but currently we only build and store the APK artifacts. A possible enhancement could be to auto deploy the APK to Play Store after every commit. But first we need to decide where to deploy it. Do we want to have a separate Dev Version in Store or do we want to use the alpha or beta channel Google Play offers? The latter one turned out to be really complicated and inconvenient. In addition we need to make sure the APK gets signed properly before uploading it to the Play Store. We should use the existing signing server if possible but maybe outline this task in a separate ticket.

What to change

Adjust config.yml to auto upload the signed APK to tbd channel

Change History (1)

comment:1 Changed 11 months ago by jchee

  • Resolution set to rejected
  • Status changed from new to closed

Closed as the ticket has been moved over to GitLab:
https://gitlab.com/eyeo/adblockplus/adblockplussbrowser/issues/18

Note: See TracTickets for help on using tickets.