1518167 - Requesting twig repo cedar be reset

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Mike de Boer [:mikedeboer]]

Cedar is unused at the moment, since the Photon project has long since ended. I'd like to use it for a different project...

This is for Firefox Desktop Search Service work. Please run the following script and reset cedar to mozilla-central:

export REPO_PATH=mozilla-central
export TWIG=cedar

cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG

Comment 1

[Connor Sheehan [:sheehan]]

I've just kicked off the reset process for you. I'll let you know when it is complete. I'll need to file a follow up bug to reset the branch in mozilla-taskcluster.

Out of curiosity, is there a wiki page or document somewhere that includes a bug template telling you about the `reset_pp_repo.sh` script? This bug report is suspiciously similar to bug 1484762. If so, I'd like to know where it is as we use an Ansible playbook for project repo resets these days and that document will need to be updated. :)

Comment 2

[Mike de Boer [:mikedeboer]]

(In reply to Connor Sheehan [:sheehan] from comment #1)
> I've just kicked off the reset process for you. I'll let you know when it is
> complete. I'll need to file a follow up bug to reset the branch in
> mozilla-taskcluster.

Thanks!

> Out of curiosity, is there a wiki page or document somewhere that includes a
> bug template telling you about the `reset_pp_repo.sh` script? This bug
> report is suspiciously similar to bug 1484762. If so, I'd like to know where
> it is as we use an Ansible playbook for project repo resets these days and
> that document will need to be updated. :)

No, I just cloned my previous reset request (bug 1306260), which I cloned from another one myself... :D 
If there's a template, I'll use it next time!

Comment 3

[Connor Sheehan [:sheehan]]

(In reply to Mike de Boer [:mikedeboer] from comment #2)

No, I just cloned my previous reset request (bug 1306260), which I cloned
from another one myself... :D
If there's a template, I'll use it next time!

Oh, okay! No worries in that case. :)

The repo has been reset to revision 0dcf945b3871. Once bug 1518207 is
resolved we can close this out as complete.

Comment 4

[Phil Ringnalda (:philor)]

There is a (broken and also outdated) template in https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories#Book_one_of_our_fabulous_.22disposable.22_project_branches which attempts to say to run reset_pp_repo.sh, but instead says to run {script_name}.

Comment 5

[Mike de Boer [:mikedeboer]]

(In reply to Phil Ringnalda (:philor) from comment #4)

There is a (broken and also outdated) template in https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories#Book_one_of_our_fabulous_.22disposable.22_project_branches which attempts to say to run reset_pp_repo.sh, but instead says to run {script_name}.

Aha! Good point, that's my source of truth. Connor, you might want to take a look at that wiki page and update instructions as needed there.

Comment 6

[Mike de Boer [:mikedeboer]]

I can't yet push to cedar; it says:

abort: authorization failed.

Comment 7

[Mike de Boer [:mikedeboer]]

Oooh hg push cedar does work, but now it says I need to wait for https://treestatus.mozilla-releng.net/trees/cedar to appear.

Comment 8

[Mike de Boer [:mikedeboer]]

To be very clear: the error as mentioned in comment 7 blocks me from being able to push:

mikedeboer:(hg)cedar[60aa249]/$ hg push cedar
pushing to ssh://hg.mozilla.org/projects/cedar
no revisions specified to push; using . to avoid pushing multiple heads
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 186 changesets with 1473 changes to 1255 files
remote:
remote:
remote: ************************** ERROR ****************************
remote: Error accessing https://treestatus.mozilla-releng.net/trees/cedar :
remote: HTTP Error 404: NOT FOUND
remote: Unable to check if the tree is open - treating as if CLOSED.
remote: To push regardless, include "CLOSED TREE" in your push comment.
remote: *************************************************************
remote:
remote:
remote: transaction abort!
remote: rollback completed
remote: pretxnchangegroup.a_treeclosure hook failed
abort: push failed on remote

Comment 9

[Connor Sheehan [:sheehan]]

Updated the Wiki page to include the current steps to reset a project branch.
Thanks for pointing me at that page!

Hm, not sure why cedar isn't showing up in Treestatus. We have a global hook
that checks for tree closures and disallows pushes on hg.mozilla.org, and
for whatever reason this project branch is not in Treestatus anymore. I'll
open a bug to re-add it.

Comment 10

[Mike de Boer [:mikedeboer]]

Ok, cool, now I can push - but each time I push a syncup of mozilla-central, it posts to all the bugs with bzpost. I don't think that's what we want?

Comment 11

[Mike de Boer [:mikedeboer]]

Never mind, this is something I need to configure myself - I need to disable the 'cedar' tree in a [bzpost] .hgrc section whenever I push.
Thanks for all your work here!