Custom Dev Ops Tool - Break fix
17 Dec 2023
Objective
Fix a break to custom Dev Ops Tool which clones Dev, Test, etc. environments from a production system (db, web server, software framework and components).
Technical Goals/Overview
Dev Ops tool has functioned for years and facilitated CI/CD of E-Commerce system. Recently, the custom tool fails to provide a working dev/test environment from production system. Identify and resolve issue.
Summary: Technical Implementation
- Identify likely causes of issue
- Consider potential dependency changes in production vs cloned environments.
- Cloned environment uses ‘latest’ dependencies.
- Cause appears to be a ‘new’ change in production system/dependencies.
- Issue identified as ‘new’ serialization of server configuration in db not handled during the cloning process.
- Resolve unhandled serialization of server configuration issue.
- Identify solution from possible fixes.
- Implement solution and verify custom Dev Ops tool is working correctly.
Overall, the technical implementation focused on successfully navigating and trouble shooting ‘broken’ custom Dev Ops tool by logically investigating where ‘breaking changes’ were likely to be introduced and eliminating potential culprits i.e. (db, web server, software framework and components) until resolved.
Skills Footprint:
| Category | Technical Specifics |
|---|---|
| general | Breaking Changes * CI/CD * Automated Testing * Automated Deployment |
| standards | HTML * CSS * JSON * Source Control * Dependency Maintenance * Dependency Management |
| tools | VSCode * Docker * GIT * BASH * SSH * Python * Pytest |
| concepts | DevOps * Containerization * Troubleshooting |
| packages | Docker CLI * PyTest * SeleniumBase |