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

Verification for Partner Repack Releases needed

RESOLVED WORKSFORME

Status

Release Engineering
Release Automation
P3
normal
RESOLVED WORKSFORME
5 years ago
4 years ago

People

(Reporter: Tomcat, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Partner Builds have a lot of potential point of failures like wrong file permissions etc, also one issue could be that the distribution.ini or repack.cfg (not sure about other files) is in the dos format instead of uni.

Having as example a dos formatted distribution.ini file will cause that the repack is created but without any partner customization, at least with the partner-repack script (not sure about the release automation). We need to make sure that Partner Repack Builds are also Partner Repack Builds and having some kind of verification of the settings being adapted etc
(Reporter)

Updated

5 years ago
Summary: Verification for Partner Pack Released needed → Verification for Partner Repack Releases needed
Component: Release Engineering: Custom Builds → Release Engineering: Releases
QA Contact: bhearsum

Updated

4 years ago
Assignee: cbook → nobody
Component: Release Engineering: Releases → Release Engineering: Automation (Release Automation)
Priority: -- → P3
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering

Comment 1

4 years ago
We've fixed this with process: https://intranet.mozilla.org/Build/Partners/Repacks/Landing_Changes
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.