Closed Bug 1148229 Opened 8 years ago Closed 8 years ago

clone puppet repo for the SeaMonkey project.


(Developer Services :: General, task)

Not set


(Not tracked)



(Reporter: ewong, Unassigned)



The SeaMonkey project wishes to have a clone of the current puppet repo.

The rationale stems from bug 1147835, specifically both and

OS: Windows 8.1 → All
I think this belong in a RelOps component?
No, he's requesting an hg repo clone, although he didn't actually give any names of repos.
Flags: needinfo?(ewong)
(In reply to Dustin J. Mitchell [:dustin] from comment #2)
> No, he's requesting an hg repo clone, although he didn't actually give any
> names of repos.

Ah sorry.  Where is the best place for the seamonkey's puppet repo?  

I'm wondering if we're allowed to have

Callek, what do you think?
Flags: needinfo?(ewong) → needinfo?(bugspam.Callek)
Blocks: 1147835
personally I like hg.m.o/build/seamonkey-puppet but I won't be opposed to a new top-level folder. Or a subfolder under build/

I think hal is the best answer for that though

Specifically what this bug needs

* A home for our puppet clone, location to be determined.
* Initial clone from hg.m.o/build/puppet
  \- Initial clone to include all branches.
* New location to have same L2 requirements as build/puppet and same hooks (the one that prevents non-releng from pushing to prod can be skipped, but I won't scream if its included for now)
Flags: needinfo?(bugspam.Callek) → needinfo?(hwine)
The rest of the seamonkey build support lives in user repos (patch configs). Why should this one be different? (Permissions could be set to L2 on the user repo, and hooks configured.)
Flags: needinfo?(hwine) → needinfo?(bugspam.Callek)
brief chat with hal just now, he'll followup here when theres more to share.
Flags: needinfo?(bugspam.Callek) → needinfo?(hwine)
Depends on: 1150329
This repo is live at:
Closed: 8 years ago
Flags: needinfo?(hwine)
Resolution: --- → FIXED
Awesome!  Thanks Hal and all those involved!
One thing.

when I push to, I got the following:

$ hg push ssh:// -e 'ssh -l'
pushing to ssh://
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 0 changes to 0 files (-1 heads)
remote: Trying to insert into pushlog.
remote: Inserted into the pushlog db successfully.
remote: View your change here:

This got me confused and concerned that I had pushed to the wrong
repo.  Can the last line be changed to reflect that I pushed to
the SeaMonkey/puppet repo and not the build/puppet one?
You need to log in before you can comment on or make changes to this bug.