Opened 12 months ago

Closed 3 months ago

#7120 closed change (rejected)

Reimplement "releaseAutomation.py" as a NodeJS script, use Git instead of Mercurial

Reported by: tlucas Assignee:
Priority: Unknown Milestone:
Module: Automation Keywords: closed-in-favor-of-gitlab
Cc: sebastian, fhd, kzar, erikvold Blocked By: #7101
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description

Background

We are attempting to establish gitlab.com as our upstream repository host. For this to happen, we need to get rid of any Mercurial dependencies in our code base.

What to change

Switch from using Mercurial to Git for the releaseAutomation. While at it, re-implement the logic in releaseAutomation.py as a NodeJS script in adblockpluschrome

Change History (4)

comment:1 Changed 12 months ago by tlucas

  • Blocked By 7101 added

comment:2 Changed 12 months ago by erikvold

  • Cc erikvold added

comment:3 Changed 3 months ago by sebastian

Most of the complexity in our release automation is because we archive release builds, but that will soon be done by other means (webext#45, webext#54), leaving following tasks:

  1. Bumping the version
  2. Adding a release tag
  3. Creating a release build (for upload to the stores)

I'm not sure if we necessarily need automation for this. Note that for releases for Microsoft Edge, I'm already doing the above steps manually for a while, since the release automation doesn't support diverging version numbers for individual release targets.

comment:4 Changed 3 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.