Community
Participate
Working Groups
Eike and I have planned a maintenance operation on the main Git repo. For this I request temporary SSH shell access for the account "swinkler" (sorry, my Bugzilla and committer accounts are currently different ones. See Bug 368080) Here's what we are planning to do: 1. Adjust tags which have been damaged by earlier maintenance operations: git tag -f committers/estepper/2.0-end-of-maintenance a84841d git tag -f committers/estepper/before-revision-holder 9a6fedc git tag -f committers/estepper/cdo2-first-roundtrip 44fad22 git tag -f committers/estepper/pop-20080726 0bf4028 git tag -f committers/smcduff/merge-20080609 35b563b git tag -f drops/2.0.2 8309921 git tag -f drops/I20110514-0431 925405c git tag -f drops/R20100614-1613 dac8755 git tag -f drops/R20100914-1022 73ab4b9 2. Shrink our repository and remove subtrees with big objects git filter-branch --tree-filter 'rm -rf incubation/ infrastructure/ deprecated/' --tag-name-filter 'cat' --prune-empty -- --all git for-each-ref --format="%(refname)" refs/original/ | xargs -n 1 git update-ref -d git reflog expire --expire=now --all git gc --prune=now (the incubation, infrastructure and deprecated subtrees have already been factored out into separate repositories. I had forgotten to delete the original paths from the main repository. Deleting them now, will require all users to clone again, but it will also improve cloning speeds by 30 to 50% and shrink the repository by that amount) 3. Ensure that repository policies are safe after the discussion of Bug 362076, we have agreed that we want to have receive.denyNonFastForwards=true receive.denyDeletes=true set on our server repository. I will check if these are already set and if not, set them so we have a minimum safety against ourselves using git in a bad way ;-) The plan is to carry out these activities next Friday 1/13 at 10:00 EST (16:00 CET). Please confirm, that you can give me shell access at that time. After the actions mentioned above have been finished (I estimate 3-4 hours), I'll report back to this Bug and you can revoke my shell access again.
(In reply to comment #0) > Here's what we are planning to do: [...] Not to forget a complete backup prior to the other steps :P
(In reply to comment #1) > (In reply to comment #0) > > Here's what we are planning to do: [...] > > Not to forget a complete backup prior to the other steps :P Implied ;-)
Ok, I'll grant you shell access to build.eclipse.org 01/13/12 for you to perform this maintenance . -M.
Hi, I still have the restricted shell on build.eclipse.org :-( Am I doing something wrong or am I too early? Cheers, Stefan (In reply to comment #3) > Ok, I'll grant you shell access to build.eclipse.org 01/13/12 for you to > perform this maintenance . > > -M.
Sorry. I lost site of this while working on some back end code. You should be all set. -M.
No problem. The maintenance is complete and successful. You can revoke my shell access and resolve the Bug. Thank you.
Ok, done. -M.
