Checklist for maintenance changes (db/code)

Owned by Noreen Dertinger
Last updated: Dec 19, 2024
3 min read

Overview

CivAv Portfolio

DevOps “tickets”:

General contacts:

  • General contacts: General Contacts & DLs - BSD - Civil Aviation - Confluence

    • note: Corporate DBA group is for database issues such as database is down, database refreshes, etc.

    • Corporate Data Management is the group that reviews changes such as updates to the database structure., code changes etc.

Good to know:

 

DevOps Boards:

DSD-CIVAV Support Team Backlog items Board - Boards

  • A red icon identifies a bug. 

  • A blue one indicates a PBI 

  • Yellow/gold identifies a task

Visual Studio Subscriptions:
My Subscriptions - Visual Studio Subscriptions Portal

Use the latest version of visual studio.

Application information pages:

  • if the information on the information page for an application you have are working for is missing or changed please update it as part of your change.

  • Examples include but not limited to:

    • System Profile Information:

    • Subject Matter Expert is AVRO Arrows Maintenance Team

    • Technology Assessment:

    • Environment Access Information:
      if the UNC information for development and acceptance is missing please add it. It can be derived based on the URL by referring to Server Paths - BSD - Civil Aviation - Confluence

    • The UNC information for production is intentionally not included in the application documentation pages.

      • Production is a restricted environment that is maintained by the web maintenance team.

        • If you need access to production files please reach out to the web technical team. They can provide you with the information you need or direct you to the appropriate resource.

      • If you fix a problem that is recurrent, add (or update if a document exists already) a document to our document repository for future development work ad to help colleagues in the team.

NuGet

Visual Studio NuGet settings - BSD - Civil Aviation - Confluence

[“application x”] does not run on localhost

Verify that the application references are valid. Some applications, such as NORMS have multiple components where the references have to be checked.

Missing/outdated packages.

Visual Studio NuGet settings - BSD - Civil Aviation - Confluence

Example:

CLF/StreamTag filter

Edit - How to install CLFPage and StreamTagFilter - BSD - Civil Aviation - Confluence

web.config

web.config checklist - BSD - Civil Aviation - Confluence

 

Access to database passwords

Access to Database Passwords - DSD - Civil Aviation - Confluence (atlassian.net)

Git

Git Bash - BSD - Civil Aviation - Confluence

Visual Studio:

How-to use Git with Visual Studio - BSD - Civil Aviation - Confluence

Coding Guidelines

General

.NET (things that are specific to .NET)

Making code changes in DevOps using Visual Studio - BSD - Civil Aviation - Confluence

gitignore

 

PowerBuilder (things that are specific to PowerBuilder)

 

Backups (development and acceptance servers)

Backup location for application deployments - BSD - Civil Aviation - Confluence

 

PowerBuilder:
PowerBuilder and Git Configuration and Procedures - BSD - Civil Aviation - Confluence

 

 

 

UNIT Tests

MS Test Unit Tests in Visual Studio - BSD - Civil Aviation - Confluence

 

Deployment procedures:

 

Current Web Servers Configuration .NET 4.7.2 and .NET Core 6

  • .NET 4.7.2 and .NET Core 6+ are the versions currently supported.

    • If developers want to use newer version they have to use “self-contained” deployment.

  • ACC servers are configured to be identical to prod. If your deployment is not working correctly on acceptance follow-up on the cause (debug it, etc).

Changes have to be deployed to, and pass testing in development and acceptance before deploying to production:

  • development (developer testing such as unit tests, etc.)

  • acceptance: (developer “smoke test” AND written confirmation/approval from client in the DevOps ticket

Changes have to be deployed to, and pass testing in development and acceptance before deploying to production:

  • development (developer testing such as unit tests, etc.)

  • acceptance: (developer “smoke test” AND written confirmation/approval from client in the DevOps ticket

.NET web apps

Manually deploying code to the development and acceptance staging servers - BSD - Civil Aviation - Confluence

 

PowerBuilder

PowerBuilder applications Deployment Procedure - BSD - Civil Aviation - Confluence

 

Reviewing pull-requests

Creating your change request