Closed
Bug 400706
Opened 17 years ago
Closed 17 years ago
push js-1.7.0.tar.gz to stage
Categories
(mozilla.org :: FTP: Staging, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bc, Assigned: zach)
References
Details
<http://people.mozilla.com/~bclary/public/spidermonkey/js-1.7.0.tar.gz> needs to be pushed to stage.mozilla.org/pub/mozilla.org/js/ for publication on <ftp://ftp.mozilla.org/pub/mozilla.org/js/> I still am able to ssh into stage and appear to still have write access to the js directory, but if I recall correctly this access was to have been removed and I am not sure that it is kosher for me to do so. What is the approved procedure for putting bits on stage?
Comment 1•17 years ago
|
||
file in FTP: Staging or email the URL to ftp-stage@mozilla.org
Assignee: server-ops → zach
Component: Server Operations → FTP: Staging
QA Contact: justin → mozpreed
Updated•17 years ago
|
Group: infra
Reporter | ||
Comment 2•17 years ago
|
||
(In reply to comment #1) > file in FTP: Staging or email the URL to ftp-stage@mozilla.org No response to email sent 10/22.
Assignee | ||
Comment 3•17 years ago
|
||
Hey Bob. I just uploaded the file into ftp.m.o/pub/mozilla.org/js. Things are obviously in a state of flux with the stage migration work. My (probably incorrect) understanding is that you can continue to login to stage and upload builds right now, until the server migrates over. Justdave's blog post (http://www.justdave.net/dave/2007/10/22/stagemo-shift-reloaded/) explains what access will be available on the new server.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 4•17 years ago
|
||
I missed that you were confused about the stage migration. Everything continues as it has on the existing stage.mozilla.org for the time being, although that will go away soon. You're welcome to try out stage-new.mozilla.org, which should also work, you just need to use sftp or scp on the new server. Eventually that machine will become stage.mozilla.org and replace the existing one.
You need to log in
before you can comment on or make changes to this bug.
Description
•