/
Deployment

Deployment

Owned by Kamil.Wojciechowski1 (Unlicensed)
Feb 28, 2024
2 min read

  1. CDP apps

    1. (KW approach)

      1. First of all, I deploy to the stage/dev/qa environment for a client to test all necessary changes if work fine.

      2. Then after approval of the process I deploy it do production.

        1. First of all, I download the current JAR to make a Backup

        2. Then I upload a new jar

        3. Inform the client that changes are deployed.

        4. Check logs if something happens.

        5. Then I decide if I should or should not deploy backup back again and fix some issues that was not noticed on the dev/stage/qa.

  2. CRC apps

    1. Almost all applications on dev do not work so with that we make changes and do the same process for CDP but without DEV/STAGE/QA deployment.

    2. This needs to be done with caution as we make changes directly do production.

    3. THERE IS A REQUIREMENT TO SAVE A BACKUP JAR FOR PRODUCTION.

  3. Enfamil apps

    1. In here there is currently no knowledge of how to deploy applications to production. QA is deployed via Azure DevOps pipelines.

    2. Mauricio currently is gathering all the requirements for deployment to production

  4. CLP apps

    1. Those applications are in Azure DevOps so I’m not aware if there are pipelines or if it should be done manually.

    2. Here it is best to ask Cyril how it was previously deployed, or what he thinks we should do with such deployment (with Mauricio)

    3. Most probably it will be similar to the CDP process.

From my side, there is a need to move all CDP, and CRC apps to Azure DevOps our group (when created) and create necessary pipelines and releases to save jar as backup and make CI/CD deployments from there. Currently, we have only CI/CD (JENKINS) for CDP but we don’t use them as we don’t know if they work.