HSI HSI-Datasync-OW code building for new release

Release Branch
1. policy:
  1. Every release need a release branch;
  2. A new release branch must be copied from current develop branch;
  3. only one release branch existed; if need a new version release branch, delete old one, then copy from develop again;
  4. After deployed in production, the release branch need be tagged and deleted.
2. Example: HSI-Datasync-OW
  1. current exists a release branch: release/R1.1, not deployed to production yet;
  2. delete the branch;
  3. create a new release branch from develop (just merged)
    
    Name R1.1 (or a new version):
    , click create branch
  4. Jenkins release build for OW will auto build a new ear file with the release shared folder (Here is for HSI project):
  5. No matter if build success or fail, there should be a notice email, if any issue/error happened, need check the log from Jenkins server.
  6. Manual release build in Jenkins:
    , click build with parameters:
    , the built ear file can be found in shared folder.
  7. Copy the ear file to a share folder (for deployment person – webmaster),
    check manifest file: e.g. Implementation-Version: 2500552afc. double check the version is the latest commit in release branch.
After deployment:
1. Merge release branch to master with pull request after deployed to PROD;,
2. Tag release branch's latest commit: e.g. hsi-datasync-ow1.0 (application name + version number)
3. Delete the release branch.
  Here is the reference link (Step 2: a-c): Git Process to Prepare for Production Deployment
4. Update release management
Additional, for deployment process: currently need ticket include documents, request deployment email – including request information and providing a shared folder for the deployed ear file to webmaster.