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

Don't notify pulse.mozilla.org of pushes to private hg repositories

RESOLVED WONTFIX

Status

Developer Services
Mercurial: hg.mozilla.org
--
major
RESOLVED WONTFIX
6 years ago
3 years ago

People

(Reporter: Jesse Ruderman, Assigned: christian)

Tracking

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/691] )

(Reporter)

Description

6 years ago
Pushing to private repositories (those to which read access is restricted) probably shouldn't cause messages to be sent to pulse.

I just pushed to a repository that's private for security reasons, with a commit message that's private for Apple-NDA reasons, and I'm worried that some info was accidentally made public through Pulse :(
(Assignee)

Comment 1

6 years ago
I'll cook up a way to blacklist ASAP
Assignee: server-ops → nobody
Status: NEW → ASSIGNED
Component: Server Operations → Hg: Customizations
QA Contact: mrz → hg.customizations
(Assignee)

Comment 2

6 years ago
A list of repos in a private bug would help the eventual rollout FWIW
(Assignee)

Updated

6 years ago
Assignee: nobody → clegnitto
(Reporter)

Comment 3

6 years ago
You can start with all the repos under hg.mozilla.org/private
Product: mozilla.org → Release Engineering
Product: Release Engineering → Developer Services

Updated

3 years ago
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/229]

Updated

3 years ago
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/229] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/691] [kanban:engops:https://kanbanize.com/ctrl_board/6/229]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/691] [kanban:engops:https://kanbanize.com/ctrl_board/6/229] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/691]

Comment 4

3 years ago
Pulse hook is not deployed. Closing.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.