Closed Bug 1192006 Opened 6 years ago Closed 6 years ago

Sort out tbbuild and tbbuild/buildbotcustom repos


(Developer Services :: Mercurial:, defect)

Not set


(Not tracked)



(Reporter: gps, Unassigned)



(1 file)

tbbuild and tbbuild/buildbotcustom are existing Mercurial repositories.

The tbbuild repository is empty. I don't know why it exists and suspect it can be deleted.

The tbbuild/buildbotcustom repo hasn't been pushed to since October 2011. Further, I don't believe the hgweb configuration actually allows access to this repo. fails because the WSGI configuration doesn't list it. Also, nested repositories is just wonky and shouldn't be supported.

What should we do with these repos?

(You can `hg clone ssh://` to access that repo if you want to poke around.)
Flags: needinfo?(bugspam.Callek)
I sadly know nothing about these repos, perhaps jcranmer or standard8 do.
Flags: needinfo?(standard8)
Flags: needinfo?(bugspam.Callek)
Flags: needinfo?(Pidgeot18)
I suspect these were either clones of the build/ versions originally used when we had a separate  build infra. I think they can just be deleted, there's unlikely to be anything we need there now.
Flags: needinfo?(standard8)
hgmo: remove tbbuild (bug 1192006); r?hwine

These repos are apparently not used and offer little to no value by
Attachment #8646481 - Flags: review?(hwine)
Attachment #8646481 - Flags: review?(hwine) → review+
Comment on attachment 8646481 [details]
MozReview Request: hgmo: remove tbbuild (bug 1192006); r?hwine

nit: redo summary/commit message to something like "remove tbbuild from web view" - I kept looking for something dealing with the physical repos :)

speaking of which, we should develop a process for archiving such repos. We have a spot where the cvs & bzr repos went. We may want to continue that practice.
Will deploy this shortly.
Closed: 6 years ago
Resolution: --- → FIXED
And I moved /repo/hg/mozilla/tbbuild to /repo/hg/dead_repositories on hgssh. Having the repo linger on hgweb machines is tolerable.
Flags: needinfo?(Pidgeot18)
You need to log in before you can comment on or make changes to this bug.