Closed Bug 451454 Opened 17 years ago Closed 16 years ago

getfirebug.com is not updating.

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: johnjbarton, Unassigned)

Details

The content of getfirebug.com/tags/production is not being reflected on to the getfirebug.com web site, specficially getfirebug.com/releases/firebug/1.2/firebug-1.2.0b14.xpi is not showing up.
As was told to you when getfirebug.com was originally set up, you need to request pushes for production site updates. If you would like for getfirebug.com to automagically pull from the production tag on a set interval, that would probably be fine, too, but that's not what was requested originally.
Assignee: nobody → server-ops
Component: Server Operations: Projects → Server Operations
OS: Linux → All
Hardware: PC → All
But I did request the automatic pull and it was working for a while. Well working in that if I waited for an hour it would come out. Now its been six hours. Waiting a hour isn't ideal but now I don't know what to do.
(In reply to comment #2) > But I did request the automatic pull and it was working for a while. Well > working in that if I waited for an hour it would come out. Now its been six > hours. Waiting a hour isn't ideal but now I don't know what to do. Ah, ok. It's probably a stale lock file with git then.
seems to be working now. File was there when I checked this morning.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updates I pushed on Friday afternoon, eg svn+ssh://mozilla_svn/projects/getfirebug.com/tags/production/releases/firebug/1.6X/firebug-1.6X.0a4.xpi do not show up on the web, eg http://getfirebug.com/releases/firebug/1.6X/ I updated from svn and verified that the file is in svn.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I think you need to talk with the folks over in bug 542554. File a new bug if needed.
Status: REOPENED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.