Skip to main content

Checklist - Deployment Process (TS, Clerical, EE, MCAP)

  • Application(s) being updated
    • Employee
  • If over 3  tickets, then Create a new ticket "Prepare release of Employee system to Production" ex Times-999
    • if new ticket created then put it into development status (In Progress)
    • add related to links for all tasks being pushed to production
    • if you have checklists in related tickets, trim them from the tasks that were moved to this ticket.
  • Move all tickets to Ready to deploy
  • Get a proposed rollout time from customer (or a range of rollout times)  (goal: off hours) - 
    • Confirm with Gene to confirm the timing is ok. Then update the ticket with rollout schedule.
    • Post a message in the #Change-Notifications channel of Slack
  • Update a release note in confluence
  • Release date -5 days
    • Notify customer
  • On Release date
    • Create a database change request script. Add this to the \app_data folder, move other task scripts to a subfolder.
    • Create database update tickets in the morning
  • Rename my c:\compiled … add 'deployed to production' to the folder name.
  • After the database change request has been processed
    • Update application, correct web.config etc
    • Move that database change request from \data\ to \data\Posted2Production
    • Submit a pull request
    • Merge that pull request in
    • Prepare an email message to Cassandra, Anna on the tasks that have been closed.
    • move the tickets that are currently in 'ready to deploy' to done
  • Move all c:\compiled_xxx to u:\builds
  • Review confluence release note
  • After database changes and programming changes
  • Release Note cleanup
    • Rename the release note in confluence from "timesheet - pending changes" to "timesheet - 9/30/2020" with the date being the date it was released to production.
    • Clone the release note. Give the new one a name like "timesheet - pending changes", and then delete its contents - it should be fresh for the next set of code changes.
    • Review my notes document, move any task-related notes to the Jira ticket, then delete those notes.
  • Update the Accomplishments note - This is needed for quarterly reporting.l
  • Close the "prepare release for production" ticket
  • Review Tickets - make sure hours = 0
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.