Closed
Bug 858052
Opened 13 years ago
Closed 12 years ago
please create 1 new STAGING git repo
Categories
(Developer Services :: General, task)
Developer Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: fubar)
References
Details
(Whiteboard: [re-vcs-sync][reit-b2g])
Please create a new git repo on git1.stage.dmz.scl3.mozilla.com <= STAGING as follows:
name: bugs/bz857696.git (change as needed)
permissions: world readable, scm_level_2 writable
hooks: none
extra configs:
git config --bool --add receive.denyNonFastForwards "true"
git config --bool --add receive.denyDeletes "true"
Thanks!
Updated•13 years ago
|
Assignee: server-ops-devservices → klibby
| Assignee | ||
Comment 1•13 years ago
|
||
I've talked with Ben and the staging environment (particularly the puppet module to manage same) is in need of updating. In your April 3 email you asked us to leave staging "as is", which conflicts with our need to update to the gitolite3 module, as well as bug 845520). How would you like to proceed?
as long as we coordinate, we're good - the major timing discussion is in bug 845520
| Assignee | ||
Comment 3•12 years ago
|
||
All set:
sekrit$ git clone http://git1.stage.dmz.scl3.mozilla.com/bugs/bz857696.git
Cloning into 'bz857696'...
warning: You appear to have cloned an empty repository.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•