828033 - Update freddo config for support-dev.allizom.org to use a new branch.

Status: RESOLVED FIXED

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

Description

[Michael Cooper [:mythmon]]

Please update the config for support-dev.allizom.org to listen to the branch 'fix-dev-828277'. This is to troubleshoot and hopefully fix failing deploys on -dev we believe are caused by a configuration error on our end.

Comment 1

[Michael Cooper [:mythmon]]

correction: The branch is named 'fix-dev-826277'. Sorry for that.

Also, if it wasn't clear, this will be reverted after the problem gets fixed and the changes land in the master branch of SUMO.

Comment 2

[Jake Maul [:jakem]]

Working on this.

Comment 3

[Jake Maul [:jakem]]

After much wringing of hands and gnashing of teeth, this is completed.

For the record, it appears you have to change 2 things, both on the admin node:

support-dev.allizom.org/kitsune/scripts/update/commander_settings.py:
UPDATE_REF = "origin/fix-dev-826277"

support-updater.allizom.org/freddo/settings_local.py (the 'ref' line):
APP_UPDATERS = {
    'dev': {
        'ref': 'refs/heads/fix-dev-826277', # optional: only update if equal to payload['ref']
        'script': '/data/support-dev/src/support-dev.allizom.org/update', # required
    },
}

Then you also need to deploy both sites:
/data/support-dev/deploy -a

And restart some stuff:
supervisorctl restart support-updater
issue-multi-command support-dev service httpd graceful
issue-multi-command support-celery-dev /data/bin/update-www.sh
issue-multi-command support-celery-dev supervisorctl restart all

You might also want to run /data/support-dev/support-dev.allizom.org/update once by hand, then once you're sure it's on the right track, do a no-op commit to see if freddo works right.

That seems to be sufficient.