Once code has passed testing in your local development environment:

• create a pull request (PR) for review.

• Once the it is approved complete the PR if you didn’t set it to be completed automatically.

• ***Packages for deployment to development, acc, prod should be based on the Main branch, not the dev branch.

• 1. deploy the package to development. Currently there is no pipeline for this many apps so the deployment deployments has to be done manually.

  • Smoke test.

• 2. deploy the package to acc.

  • requester approves the change. work with the requester/provide steps to test the change if needed.

• Currently, an SMGS ticket is needed to deploy to prod.

  • see: Creating a Change Request in SM-GS - DSD - Civil Aviation - Confluence (atlassian.net)

Identifying the development environment path to deploy to:

...

• A meeting is scheduled for August 21, 2023 to explain the new eMER and CAMIS pipelines.

Identifying the environment path to deploy to:

1. The location to deploy to is listed in the Environment Access Information section, under “UNC”, or wwwfiles.

   The path to deploy to is listed under “UNC”.

   1. If not: go to Applications and select the page for the project that you are deploying.

      1. For example, if deploying eMER to the development environment, select the eMER page

2. The location to deploy to is listed in the Environment Access Information section.

4. Some projects might have more than one development environment environment.

   1. For example, eMER is deployed to:

      1. an unsecure instance where authorized users are automatically logged in when they click the URL.

      2. a secure location such as GCKey.

Deploying your code:

1. Navigate to the unc path corresponding to the staging server for the application you are deploying.

   1. For example, navigate to the path for the eMER unsecure development environment

...

zip the files for the application and copy it to the backup location for the app you are deploying.
Optionally, you can also copy the content of the folder to a temporary location on your local machine.

1. Important: you will need the web config that you have copied as the last step of your deployment process.

...

Publish your changes locally

1. Create publish settings in visual studio

2. create a different folder - don’t use the one from step 2.

3. create a new custom profile

4. Keep the default location bin\app.publish

5. Finish

6. Save

7. Publish

Publish your changes locally

1. select the publish settings file in visual studio

2. make sure that the target folder for the package is on your local machine. Don’t publish directly to the server.

3. Delete the web.config from the package you published.

4. Go to to the staging server for the application you are deploying (per identifying the path to deploy to).

4. Backup the existing deployment. For all apps, except CAMIS and eMER,
   refer to Backup location for application deployments

5. Update the development location with your changes:

...

Go to the deployment location for the project

4. 1. delete everything except for the web.config

...

4. 1. , and any special required folders that are not included in the package.

   2. copy the files (except web config) from the folder you created in step 3 and paste them in the deployment location.

5. wait 5 or 10 minutes.

6. Test that the project you deployed is working.

Reverting a PR

• revert in dev and then merge dev into main.

Oracle library

Different versions of the Oracle library are required for running some applications locally vs deploying them to development, acceptance and prod.

Projects we know this applies to:

• eMER

• CAMISOthers?

• Refer to Selecting the correct oracle library for the steps.