Opened on 04/21/2014 at 02:41:48 PM
Closed on 05/07/2014 at 10:16:10 AM
Last modified on 10/22/2014 at 11:32:51 AM
#364 closed change (fixed)
Publish the devbuild on the Chrome Web Store
Reported by: | sebastian | Assignee: | trev |
---|---|---|---|
Priority: | P1 | Milestone: | |
Module: | Automation | Keywords: | |
Cc: | trev, fhd, philll | Blocked By: | #356, #377 |
Blocking: | Platform: | ||
Ready: | yes | Confidential: | no |
Tester: | Verified working: | no | |
Review URL(s): |
http://codereview.adblockplus.org/6324711747223552 |
Description
Background
Starting with Chrome 35 (currently in beta) Chrome extensions that weren't installed from the Chrome Web Store are disabled on every startup. This makes using our devbuilds highly inconvenient and has a high potential to alienate almost all of our devbuild users.
What to change
- Add the devbuild to the Chrome Web Store, preserving our existing private key as explained here. But be careful not to publish the item publicly before you made sure that key.pem isn't leaked with the generated CRX.
- Create a Client ID and obtain a refresh_token as explained here.
- Configure the devbuilds to automatically update the item in the Chrome Web Store. Therefore set abpchrome_clientID, abpchrome_clientSecret and abpchrome_refreshToken in sitescripts.ini to the details obtained in the previous step.
Attachments (0)
Change History (13)
comment:1 Changed on 04/23/2014 at 01:45:27 PM by trev
- Owner set to trev
- Ready set
- Status changed from new to assigned
comment:2 Changed on 04/24/2014 at 09:34:38 AM by sebastian
- Blocked By 377 added
comment:3 Changed on 04/25/2014 at 08:14:54 AM by trev
- Review URL(s) modified (diff)
- Status changed from assigned to reviewing
comment:4 Changed on 04/25/2014 at 10:35:17 AM by trev
comment:5 Changed on 04/25/2014 at 10:56:02 AM by trev
Got all the necessary configuration parameters but didn't enable them yet - our devbuild was flagged for review so I cannot test the update scenario yet. And before I test I'm not really comfortable pushing the build tools changes in http://codereview.adblockplus.org/5163192602853376 which are required to upload to CWS automatically.
comment:6 Changed on 04/25/2014 at 10:56:11 AM by trev
- Status changed from reviewing to assigned
comment:7 Changed on 04/29/2014 at 09:29:11 AM by trev
- Keywords externaldependency added
comment:8 Changed on 04/30/2014 at 09:50:33 AM by philll
- Status changed from assigned to new
The assigned state will be dropped by #403
comment:9 Changed on 05/05/2014 at 11:05:28 AM by trev
- Keywords externaldependency removed
- Resolution set to fixed
- Status changed from new to closed
comment:10 Changed on 05/05/2014 at 01:20:14 PM by trev
Reopening because #356 is reopened, had to disable uploading again because of that.
comment:11 Changed on 05/05/2014 at 01:20:22 PM by trev
- Resolution fixed deleted
- Status changed from closed to reopened
comment:12 Changed on 05/07/2014 at 10:16:10 AM by sebastian
- Resolution set to fixed
- Status changed from reopened to closed
comment:13 Changed on 10/22/2014 at 11:32:51 AM by sebastian
- Cc sebastian removed
Pushed new string for the name: https://hg.adblockplus.org/adblockpluschrome/rev/5f49e712faf8
Uploaded the development build, it should become visible under https://chrome.google.com/webstore/detail/ldcecbkkoecffmfljeihcmifjjdoepkn shortly.