Closed Bug 806141 Opened 12 years ago Closed 12 years ago

Set up cron job to automatically sync the Firebug Swarms repo on github with getfirebug.com

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P4)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sebo, Assigned: dmaher)

References

()

Details

(Whiteboard: [triaged 20121102])

Current Firebug development happens on github. For this reason we also moved the Firebug Swarms repository there now, which was formerly placed in a Subversion repository on Google Code.

This change requires that a new cron job is set up, which synchronizes the github repository with our website, and the old one that synced from SVN to be deleted.

Old repository URL:
https://fbug.googlecode.com/svn/extensions/swarm/branches/swarm1.7/swarms

New repository URL:
https://github.com/firebug/swarms

Must be synced with:
https://getfirebug.com/swarms

Sebastian
Assignee: server-ops-webops → dmaher
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Whiteboard: [triaged 20121102]
For reference, on our side getfirebug.com is managed as an SVN repo, and swarms/ is in turn an external SVN item to said repo.  I'll have to break that functionality, clean up the pieces, and set up a new deployment mechanism.

It's perfectly do-able - I just wanted to make a note of it here. :)
Status: NEW → ASSIGNED
I haven't touched anything except swarms/ - assuming those elements which you've noted in comment #2 are currently functional, their behaviour should not have changed.

I have completed the operation and updated the production webheads.  Closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.