867469 - [basket] Push new version to staging and prod

Status: RESOLVED FIXED

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

Description

[Paul [:pmac] McLanahan]

Push the revision tagged: v2013.2

Thanks

Comment 1

[Daniel Maher [:phrawzty]]

Hello,

I pushed stage and prod, as requested.

On a separate but related note, I noticed some (minor) inconsistencies between the dev, stage, and prod deployment scripts.  Most of them were innocuous (so I fixed them outright), but there was one that I wasn't so sure on :


# Prod
    python manage.py syncdb --noinput
    python manage.py migrate --noinput

# Staging
    python manage.py syncdb
    python manage.py migrate --noinput

# Dev
    # No equivalent


Three different environments could easily mean three different procedures, but in the case of the argument to "syncdb" between stage and prod, I can only assume that they should be consistent - if so, should the argument be there or not ?

The equivalent code block does not exist in the dev deployment script - should it ?

Comment 2

[Paul [:pmac] McLanahan]

Great catch! They should all match what you have for Prod above.

Comment 3

[Daniel Maher [:phrawzty]]

Done and done - the deploy scripts for each environment, respectively, are aligned.