/
Appendix: (3) How to deploy an application
Appendix: (3) How to deploy an application
Seq | Jira→ | Local→ | Bitbucket→ | Team/TCS IT→ | build folder→ | Corp IT→ | Websphere |
---|---|---|---|---|---|---|---|
1 | Issue a ticket (e.g. HSIF-3051 * ) | create a feature branch (copy) from develop branch in Jira Ticket. (e.g. feature/HSIF-3051 branch) | |||||
2 | check out feature code | check in code in the feature branch (e.g. feature/HSIF-3051 branch) avoid of code lost | other developer can help, review and test | ||||
3 | ready to deploy to QA (remember change application's version) | raise pull request to merge feature branch to develop branch (e.g. feature/HSIF-3051 merge to develop) | review and approval (TCS IT) | ||||
4 | Merge into develop branch after approved | ||||||
5 | create release branch (copy) from develop branch (e.g. release/2022.02) | a new built ear file | |||||
6 | check new ear file's commit version | ||||||
7 | send email to request deploy the ear file (provide application information and file location) | email to Webmaster | webmaster who on duty will deploy the ear file to Websphere QA. | ||||
8 | QA/UAT testing | ||||||
9 | After QA testing, request Harry help raise a production release ticket | Harry Fong will request a production deploy ticket | |||||
10 | update deployment documents (ticket no. as prefix of document names) | Harry will upload the documents and request approval. | |||||
11 | After ticket approved, Harry engage a resource of IAG to deploy | ||||||
12 | IAG | IAG deploy the ear file to Websphere Production | |||||
13 | quick verify and confirm deploy successful | ||||||
14 | monitor the status and result. | ||||||
15 | raise pull request from develop branch to master branch | review and approval (TCS IT) | |||||
16 | Merge develop branch to master branch after approved; set release tag on commit. delete feature branch and release branch. | ||||||
17 | if no issues, update Releasement records | ||||||
18 | update ticket status |
Appendix:
- Seq 5: snapshot of build folder of generated ear file:
- Seq 7: sample of email to request webmaster help do QA deployment:
- Seq 10: release documents can be found samples in the releasement link: HSI Release Management - Release 1.x
- Seq 16: remember setup the tag in commits.