Checklist - Basic Programming Task
Application(s) being updated:
Deployment Requirements (put DB update, etc information here)
* Dev
* Test
* Production
Steps
* (1) Status=Development
* Confirm problem in localhost
* Fix problem
* Confirm fix in localhost
* Update Release Notes
* Update user documentation
* commit, then create pull request
* status=CodeReview
* Merge
* Status=QA
The Pre-Bamboo process - if you still deploy to old servers
* switch to Develop branch, Pull, Compile, build, publish to temp space
* if old server is still running, deliver to Dev on old server
* if new server does not deploy builds, deliver to dev on new server
* Test in development (old server) - confirm problem repaired (if test fails then repeat steps from Status=Development)
The Post Bamboo process - if you use bamboo to deploy dev to new servers
* After you merge, the application will be built and delivered to the Development Server
* Test in development (new server) - confirm problem repaired (if test fails then repeat steps from Status=Development)
Send to testing (Skip if there is not a testing instance)
* In Bitbucket, create a pull request (for example ‘times-454 - TS - develop -> test’) (TS, or EE, or DMS - any code to help identify the program)
* Update QA Database (if necessary)
* After the PR is approved, merge the develop -> test branch
If you deploy to old test sasd servers, or if bamboo doesn't deploy to the test server
* On localhost, switch to test branch, do a pull
* build a new release using the test branch
If you have old test servers (sasddiis1 - test instance)
* Deliver to old server QA instance
* Test old website - confirm problem repair
New Test Servers (sdt-iis1) (If bamboo is NOT deploying to new test servers)
* Place delivery set Onto Q Drive someplace
* Send request to DTECH to copy files to test server
New Test Servers (sdt-iis1) (If bamboo is deploying to new server) - if you use bamboo to deploy to new test servers
* Use bamboo to build and deploy to test instance
* Test - new website - confirm problem repair (If problem is found, go back to step (1))
Prepare for delivery
* Status=InUat
* If this task is a blocker to another task then notify the person with the blocked task for instructions to proceed.
* Send to customer / ba for testing
* get delivery date
* Post announcement in @Change Management
* In Bitbucket, create a pull request (for example ‘times-454 - test → master’) (if multiple tickets are going to master, then specify the deployment Jira ticket number) (if othApps then add a code to help identity the application (for example 'othapps-594 - new hire - test → master')
* After approved, merge the test to master
* On localhost, switch to master branch, do a pull
* build a new release using the master branch
* Status=Ready to Deploy
On the day of the rollout
* if there is a change to the production database, then create a ticket
At the time of the rollout
* Update Production Database
* Update Website
* Review and update Nutrition Label
* Update all tickets associated with this update. Status = closed
Copy / paste this into bottom portion description of task