Opened 6 years ago

Closed 5 years ago

#520 closed change (fixed)

Automate generation of PAD files

Reported by: sebastian Assignee: sebastian
Priority: P3 Milestone:
Module: Infrastructure Keywords:
Cc: trev Blocked By:
Blocking: Platform: Unknown
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):

http://codereview.adblockplus.org/5723465818570752/
http://codereview.adblockplus.org/6700499810123776/
http://codereview.adblockplus.org/6294505410002944/

Description

Background

We host some PAD files for our extensions, used by download portals. However those files are currently updated manually and therefore outdated most of the time.

What to change

Automatically generate the PAD files from the metadata given in the packages.

Change History (10)

comment:1 Changed 6 years ago by sebastian

  • Cc trev added

comment:2 Changed 6 years ago by sebastian

  • Owner set to sebastian

comment:3 Changed 6 years ago by sebastian

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:5 Changed 6 years ago by sebastian

Please configure PAD file generation for following extensions in sitescripts.ini on the server:

  • Adblock Plus for Firefox
    • Also change the abp_name to "Adblock Plus for Mozilla Firefox"
  • Adblock Plus for Chrome
  • Adblock Plus for Opera
  • Adblock Plus for Safari
  • Adblock Plus for Internet Explorer
  • Adblock Plus for Android
  • URL fixer
    • Also add another older build to the downloads repo. Otherwise URL fixer will be indicated as a "New Release" in the PAD file.

And set up following redirect:

comment:6 Changed 5 years ago by sebastian

  • Review URL(s) modified (diff)

Uploaded new patch set, adding German and Russian translations.

comment:7 Changed 5 years ago by sebastian

  • Review URL(s) modified (diff)

Uploaded new patch set, adding Spanish translation.

comment:9 Changed 5 years ago by sebastian

Feel free to close this issue, after setting up the PAD files on the server, as described above.

comment:10 Changed 5 years ago by trev

  • Resolution set to fixed
  • Status changed from reviewing to closed

Resolving as fixed, filed #1628, #1629 and #1630 as follow-up issues.

Note: See TracTickets for help on using tickets.