forked from mdemers/fl_islandora_forms
-
Notifications
You must be signed in to change notification settings - Fork 2
Forms Commits and Deployment
Lydia Motyka edited this page May 26, 2016
·
2 revisions
Placeholder/DRAFT for form updates/deployment procedure. --LTM
| Order | Step | Description | Details/Links |
|---|---|---|---|
| 1 | Download the most recently deployed form from GitHub repo (XML version) | -- | How to find the form |
| 2 | Import the XML on the DEV server | Name the form with form name, your initials, and the date of import | e.g., Full_MODS_LTM_4-5-16 |
| 3 | Make and test changes on DEV, confirm that form works | -- | -- |
| 4 | Check with the rest of the team to determine if anyone else is working on changes and coordinate deploy date | -- | -- |
| 5 | If multiple staff need to deploy changes, combine changes into a single form and test on DEV | Testing should include download of MODS file edited with the new form and validation of that file. | -- |
| 6 | diff the XML of the latest deployed version of the form against the tested pre-production XML as an extra check | This really catches problems: diff -y on a linux box, output to a file, is a good way to do this, e.g., "diff -y newform.xml prodform.xml > new_prod_diff.txt" | -- |
| 7 | Commit new XML file to GitHub | Do the Commit before deploying final file to DEV | How to commit |
| 8 | Deploy to DEV and test again | Deploy = replace the current DEV version with the imported/copied new XML | Delete the old version of the form on DEV, import/copy the new version using the authoritative name (Full MODS, etc.) |
| 9 | Recreate form associations on DEV | -- | -- |
| 10 | Deploy to test and record date | Record in main page | -- |
| 11 | Test on islandora-test | -- | -- |
| 12 | Deploy to Prod and record date | -- | -- |