AMO preview site stopped auto-pulling / running a cron job which pulls from SVN trunk

VERIFIED FIXED

Status

VERIFIED FIXED
10 years ago
4 years ago

People

(Reporter: stephend, Assigned: reed)

Tracking

Details

(Reporter)

Description

10 years ago
Our AMO preview site https://preview.addons.mozilla.org/en-US/firefox/ has stopped auto-updating; it has a cron job that's supposed to pull ~ every 15 minutes from the latest SVN (trunk?)

For instance, it's missing both bug 448001 (r17398) and bug 447989 (r17401), which have landed and been verified in production, but are missing on https://preview.addons.mozilla.org/en-US/firefox/

Comment 1

10 years ago
Since we've had this auto-update break many times now, is it possible to put it into nagios (or similar) somehow, so that problems can be noticed before somebody scratches their head saying "wait a minute, my commit isn't showing up"?
(Assignee)

Updated

10 years ago
Assignee: server-ops → reed
(Assignee)

Comment 2

10 years ago
This is why it's broken:

[root@mradm02 addons.mozilla.org-preview]# svn up
Conflict discovered in 'site/app/config/revisions.php'.
Select: (p) postpone, (df) diff-full, (e) edit,
        (h) help for more options: 

The build script we were asked to add to preview is changing a file that's in svn... that won't work, as every time somebody commits a change to that file, it'll conflict on the server. I'm disabling the build script until something else is worked out.
Status: NEW → ASSIGNED
(Assignee)

Comment 3

10 years ago
ok, it's updated. Reopened bug 446648 to deal with build script problems.

(In reply to comment #1)
> Since we've had this auto-update break many times now, is it possible to put it
> into nagios (or similar) somehow, so that problems can be noticed before
> somebody scratches their head saying "wait a minute, my commit isn't showing
> up"?

What do you recommend as a way to check this?
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

10 years ago
Verified FIXED; both of those bugs are in and now fixed.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.