If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Set up app signing WSGI instance on dev signing server

RESOLVED FIXED

Status

Cloud Services
Operations: Marketplace
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: rtilder, Unassigned)

Tracking

other
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-basecamp:+)

Details

(Reporter)

Description

5 years ago
Please set up a second instance of trunion on the dev signing server for app signing.  There should be two instances of trunion running on the box and listening on different ports when this ticket is complete: the existing one for signing receipts and a new one for signing app manifests.

Comment 1

5 years ago
It looks like we don't have a proper dev environment for signing, so that will be the first step.

Updated

5 years ago
Depends on: 811504

Updated

5 years ago
Depends on: 811505

Updated

5 years ago
No longer depends on: 811504
This bug is blocking FFOS. 
Cannot land support for packagd/privileged apps in the marketplace without.
Blocks: 777048
blocking-basecamp: --- → ?

Comment 3

5 years ago
The internal only dev instance is up at http://app-signer.dev.addons.phx1.mozilla.com/.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
blocking-basecamp: ? → +
Component: Server Operations: AMO Operations → Operations: Marketplace
Product: mozilla.org → Mozilla Services
You need to log in before you can comment on or make changes to this bug.