Closed Bug 1283626 Opened 8 years ago Closed 8 years ago

disable all vcs-sync access to git.mozilla.org

Categories

(Developer Services :: General, task)

Product:
Developer Services
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

This is disabling the vcs-sync machinery from attempting reads and writes -- the move of the actual repositories is handled in other bugs.
all read and write access to repos (except fuzzing - bug 1277435) has been removed from gitolite.
all configurations for reading or writing to git.mozilla.org from legacy vcs-sync have been removed. (except fuzzing bug 1277435)
fuzzing issue resolved per bug 1277435 comment 10, so removed from configs. All vcs-sync activity on git.mozilla.org has been disabled.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
https://hg.mozilla.org/build/mozharness/rev/6935015ee9f9f7b9988d587a3121f00c75cbb000 bug 1283626 - fix incomplete removal, causing lack of update on github
Incomplete fix from last time led to github copy not being updated. The git.mozilla.org destination came first in the list -- the runtime error prevented the repo being pushed to github. The commit to github is what triggers the travis tests, so this change has to be pushed live without benefit of the travis tests. Local tests do pass.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
and we're running without errors again.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.