Auto Updater
Usage
The auto updater runs at a set time, and when it does, it will send out emails to the maintainers of the site, containing information on the update, and links which can be used to test and complete the process.
- Load the email sent. It will have a title such as "Automatic updates for
" - Open the auto updater site: https://up.agile.coop
- Login
- Start the auto-updater Lando server
- Click the link next to 'Check the updates at' in the auto-updater email
- Test the site
- Click the link next to 'To finalise this hotfix branch visit' in the auto-update email
- Go through the options in order by clicking 'approve' below the items (and then testing after each one)
- 1_finalise_hotfix : this will merge the hotfix into the master branch
- 2_deploy_master_to_stage : this will deploy the master branch to stage (note this does not sync the database)
- 3_deploy_master_to_production : this will deploy the master branch to production
Start the auto-updater Lando server
- In the auto-updater email, click the link next to
Access Jenkins jobs(alternatively, click the 'name' of the site on the Jenkins landing page) - Click the 'Schedule a build' icon next to
start_lando
- When the build is running, you will be able to click a dropdown arrow next to it on the LHS which will allow you to
watch the 'console output' so you know once it is complete
SSH access
tbc
Troubleshooting
Going to https://up.agile.coop gives me errors
Try using an incognito browser, or flushing your browser cache.
The commit does not appear to contain the updates I expect
This can happen if there was an error during the update (this could be caused by many things). First check the branch to see if the code was committed. The branch name will be in the email next to 'Updates pushed to branch'.
Next you could check the console log for the build by:
- Go to the site page in Jenkins
- Click 'update_site' for the project (note: this will not run the build)
- Click the dropdown arrow next to the latest number in the 'Build History' (eg. #3)
- Select 'Console output'
- Read through the output to see where it failed.
If nothing obviouslky fixable appears, the next best solution may be to ignore the auto updater, and manually run the updates on a seperate hotficx branch. It may be worth checking with others first, in case there is a global issue that needs resolving or applying first.
Last updated: