Closed Bug 878960 Opened 11 years ago Closed 11 years ago

[PERFORM ON 2013-07-16] Move mozilla.org::Server Operations: RelEng bugs to Infrastructure & Operations::RelOps

Categories

(bugzilla.mozilla.org :: Administration, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: arich, Unassigned)

References

Details

I'd like to do a wholesale move of "Server Operations: RelEng" to a component named "RelOps" in the new IT product.
Since this bug is for migrations, we'd like to give folks a heads up before we start moving things. Now that the top level property has been made, do you have a time estimate on how soon this one will be done?
the move requires someone from IT to run a one or two simple commands at the shell. we can do this on a date which you specify.
Sorry it's taken me a while to get back to this. I wanted to give people a month of heads up to update their scripts, searches, etc. Can we please make this move on 2013-07-16?
It will be determined whether IT would be able to do it on that date so it is best for them to answer when we move it over to the mozilla.org product. Before we do that, we need to create the new component that the bugs will be moved to. Can we get a brief summary for the new component or should it just be the same as the old description? https://wiki.mozilla.org/BMO/Requesting_Changes#Components dkl
Flags: needinfo?(arich)
Lets go with: "IT requests related to deploying and managing the RelEng infrastructure"
Flags: needinfo?(arich)
(In reply to Amy Rich [:arich] [:arr] from comment #5) > Lets go with: "IT requests related to deploying and managing the RelEng > infrastructure" Component created. Moving to IT as they will need to perform the scripts needed to move the components on the production servers. ** PLEASE DO NOT DO UNTIL 2013-07-16 ** 1. # cd /path/to/bugzilla/root 2. # perl contrib/reorg-tools/syncmsandversions.pl mozilla.org "Infrastructure & Operations" 3. # perl ./contrib/reorg-tools/movebugs.pl "mozilla.org" "Server Operations: RelEng" \ "Infrastructure & Operations" "RelOps" Then move this bug back here so we can delete the old component. Thanks dkl
Assignee: nobody → server-ops-devservices
Component: Administration → Server Operations: Developer Services
OS: Mac OS X → All
Product: bugzilla.mozilla.org → mozilla.org
QA Contact: nmaul
Hardware: x86 → All
Summary: components migration to Infrastructure & Operations → [PERFORM ON 2013-07-16] Move mozilla.org::Server Operations: RelEng bugs to Infrastructure & Operations::RelOps
Version: Production → other
Assignee: server-ops-devservices → klibby
bugzillaadm# time perl contrib/reorg-tools/syncmsandversions.pl mozilla.org "Infrastructure & Operations" real 0m0.438s user 0m0.372s sys 0m0.042s bugzillaadm# time perl contrib/reorg-tools/movebugs.pl "mozilla.org" "Server Operations: RelEng" "Infrastructure & Operations" "RelOps" About to move 2317 bugs From 'mozilla.org' : 'Server Operations: RelEng' To 'Infrastructure & Operations' : 'RelOps' Press <Ctrl-C> to stop or <Enter> to continue... Moving 2317 bugs from mozilla.org:Server Operations: RelEng to Infrastructure & Operations:RelOps real 0m9.755s user 0m0.796s sys 0m0.078s
Assignee: klibby → nobody
Component: Server Operations: Developer Services → Administration
Product: mozilla.org → bugzilla.mozilla.org
QA Contact: nmaul
Hm, I expected that the rest of the config from the old component would be copied over (QA contact, flags, etc). That doesn't appear to be the case. Did I need to request that specifically?
(In reply to Amy Rich [:arich] [:arr] from comment #8) > Hm, I expected that the rest of the config from the old component would be > copied over (QA contact, flags, etc). That doesn't appear to be the case. > Did I need to request that specifically? I have updated the qa contact and default cc to be the same as the old component. This is only relevant when the bug is created. The old bugs that were moved should have the old qa contact and cc list members still intact so not an issue. Do you have some bug id examples where flags were not retained during the move so we can look at fixing those up? dkl
Flags: needinfo?(arich)
The two things I notice: 1) The default assignee used to be server-ops-releng@mozilla-org.bugs. I'd still like this to be distinct for the RelOps and RelOps: Puppet components, but I'm not sure if it has to be tied to an actual mail alias or..? If not, let's call it: relops@infra-ops.bugs to match what other groups have done. 2) We're missing the colo-trip flag: https://bugzilla.mozilla.org/page.cgi?id=fields.html#cf_colo_site
Flags: needinfo?(arich)
(In reply to Amy Rich [:arich] [:arr] from comment #10) > The two things I notice: > > 1) The default assignee used to be server-ops-releng@mozilla-org.bugs. I'd > still like this to be distinct for the RelOps and RelOps: Puppet components, > but I'm not sure if it has to be tied to an actual mail alias or..? If not, > let's call it: relops@infra-ops.bugs to match what other groups have done. Done > 2) We're missing the colo-trip flag: > https://bugzilla.mozilla.org/page.cgi?id=fields.html#cf_colo_site Ah. Luckily that is actually a custom field on the backend so there is no data loss possibility. It just needs to be told to be visible to the new product and component(s). I have checked in the code change needed for this and will be applied in the next code push this Thursday. Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2 modified extensions/BMO/lib/Data.pm Committed revision 8876. Also old component deleted. dkl
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Fantastic, thanks!
You need to log in before you can comment on or make changes to this bug.