Closed Bug 1278979 Opened 8 years ago Closed 8 years ago

gecko-dev aurora & beta behind due to non-FF changes in hg

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

(Whiteboard: [vcs-sync]) 

For some reason, there were problems with the recent uplift which required stripping on both mozilla-aurora and mozilla-beta at different times.

In turn, that caused non-fast-forward changes to be presented to the (modern) vcs-sync process producing gecko-dev, so updates to those branches stopped on both github and git.mozilla.org.

Fortunately, neither of these branches is being pushed to (partner facing) gecko.git, so we have the option to just accept the non-FFwd changes.
Work done to "reset" vcs-sync process:
 - nuke build/target/beagle git repo on conversion machine
 - wait the 2 hours for the local repo to be regenerated

That is sufficient to get changes pushed to github again. Most devs pull from github, so they are all unblocked (as of ~2300 PT Tuesday).

For git.mozilla.org, the "denyNonForwards" config for the repo must be (temporarily) set to 'false'.
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Changes deployed to gitolite config - awaiting clean push from automation before disabling again.
This is fallout from the migration in bug 1267295
Blocks: 1267295
clean pushes via automation observed in email

config change from comment 2 reverted

everything done
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.