Filing this as a placeholder, given the recent email. We'll need to change: * Repo name * Set up a new github group with that name, so we can add people for commit access (eg sheriffs, Graeme) * App/URLs in stackato.yml * Redeploy to stackato (paas.mozilla.org this time) * File the bug for SSL for X.mozilla.org etcd * Update Treeherder links * Change the app name in various places in the repo (eg page titles) * Update the bugzilla component name * Update wikis/docs/... * Communicate to newsgroups etc

Also: * Add a new stackato group with name matching the new name, and with a handful of people added as members (per bug 1140889 comment 5)

We settled on BugHerder in today's sheriff meeting. So unless anybody else objects, shall we go with that? :)

Works for me :-) Should we use BugHerder or Bugherder (the latter matches Treeherder and Perfherder but I'm not fussed either way).

I'm all about consistency.

Wes, am I correct in thinking you wanted to own this? If so, happy for you to change the assignee, if not I'll be able to take a look sometime this week - not a problem either way :-)

Happy to take it, though you probably have more experience moving things around on Github and stackato than I do at this point.

It shouldn't be too bad - the Github part just requires a rename & then updating push URLs (though the old URLs will redirect, so everything will keep working even without that). And happy to go through the Stackato parts together? The initial blockers that will need new bugs filed (or at least other people involved) are: 1) Get a new stackato group created called "bugherder" and you, me added to it. 2) Get a new Github group created with you/me/everyone else added, and the mcMerge repo added to it.

I've renamed the github repo. https://github.com/mozilla/Bugherder is now live. Hoping nothing breaks.

Hrm, I don't have adminy powers in the mozilla github organization, so I can't make a new group myself. Right now the two groups listed for the repository are the mozilla organization owners and the sheriffs group. It looks like Dave's listed in the Owners group and could probably create a bugherder group with the relevant people added. Or we could just add Graeme separately, as I think that'd be everyone (Owners + Sheriffs + Graeme). Thoughts, Ed, Dave?

This changes most of the in-repo strings from "mcMerge" to "Bugherder".

I have created a bugherder group on Github with all paid sheriffs and Graeme added to the group

I added that group to the repository collaborators. Thanks!

Comment on attachment 8591841 [details] Link to pull request #7 r=me with the extra s/mcmerge/bugherder/ mentions in the PR comments :-) Thank you for doing this!

Addressed the comments, tested locally, and merged: https://github.com/mozilla/Bugherder/commit/821a27286e4eca667fe26c9844a6a6153257287d

So, from the list of things Ed has said need to happen to finish this: ✓ Repo name -- https://github.com/mozilla/Bugherder ✓ Set up a new github group with that name, so we can add people for commit access (eg sheriffs, Graeme) -- Dave made that group, I added it to the repo. ✓ App/URLs in stackato.yml -- The file was updated. We need to get the domains set up properly before we redeploy. * Redeploy to stackato (paas.mozilla.org this time) * File the bug for SSL for X.mozilla.org etcd ✓* Update Treeherder links -- Ish. The text of the link was updated, the link is still waiting for the new domain to be set up. ✓ Change the app name in various places in the repo (eg page titles) -- This should all be done. ✓ Update the bugzilla component name -- Done. * Update wikis/docs/... * Communicate to newsgroups etc * Add a new stackato group with name matching the new name, and with a handful of people added as members (per bug 1140889 comment 5)

And a followup to s/allizom/mozilla/ https://github.com/mozilla/Bugherder/commit/810f735acc54ced6d351bfdaf314ba4912df95b3

This is the next prerequisite for deploying to bugherder.paas.mozilla.org: > * Add a new stackato group with name matching the new name, and with a > handful of people added as members (per bug 1140889 comment 5) You'll need to file a bug to get them to add that group.

So the Stackato group has been created. Next we need to redeploy it with the new group and domain, right? Should we leave the allizom domain in the list <https://github.com/mozilla/bugherder/blob/810f735acc54ced6d351bfdaf314ba4912df95b3/stackato.yml#L25-L27> so we don't have to change the links everywhere right away? Or would it just continue working indefinitely on its own?

Since we've changed the 'name' property since the current deploy, if you re-deploy using the new config it won't affect the old. So you can just deploy using the latest config, we can switch the Treeherder links over etc (plus update the TBPL redirect) and then I can take down the old project name. When deploying don't forget to switch to the group before pushing :-)

Remaining steps: * Redeploy to stackato under the new group (the paas.mozilla.org stackato instance this time, rather than allizom) (See docs at https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30081453) * File the bug for SSL certs etc for bugherder.mozilla.org * Update Treeherder links * Update TBPL redirects (see bug 1149753 comment 6) * Update wikis/docs/... * Communicate to newsgroups etc * I can modify the old stackato project to 301 redirect to the new instance

Bug 1183368 has fixed the upstream buildpack issues, and temporarily switched us back to paas.allizom.org (vs paas.mozilla.org), and I've filed bug 1183404 for asking webops to dig into why the mozilla.org instance is not working. For now bugherder is also deployed at: https://bugherder.paas.allizom.org/ (least the subdomain now matches the new app name)

Given the comments in bug 1185320 (sec review for bugherder) that mention paas is being phased out, plus the issues we have with the current cloudfoundry buildpack (comment 21; since our stackato instance is so old) - I've looked into Heroku (as suggested in bug 1185320). I think this is going to be the way forwards, I have a demo running at: https://mozilla-bugherder-test.herokuapp.com/ I'll file a bug etc for this tomorrow.

(In reply to Ed Morley [:emorley] from comment #22) > Given the comments in bug 1185320 (sec review for bugherder) that mention > paas is being phased out, plus the issues we have with the current > cloudfoundry buildpack (comment 21; since our stackato instance is so old) - > I've looked into Heroku (as suggested in bug 1185320). > > I think this is going to be the way forwards, I have a demo running at: > https://mozilla-bugherder-test.herokuapp.com/ > > I'll file a bug etc for this tomorrow. As far as I can tell, Bugherder *should* qualify for the free tier (or at most the hobby tier if Bugherder doesn't sleep enough to get that 6 hours of downtime): There should be at least six hours out of the day where it's not used. It should only need the one worker. We don't need a database, and we probably don't need metrics. Right?

I've included an answer to comment 23 in bug 1204521 :-)

Making Bugherder be available at bugherder.m.o will happen as part of bug 1204521, so morphing this to be about the other changes required for the rename, which have been long done :-)