Build and Package Management

📌 Remember: The goal of this module is not to memorise every command. Focus on understanding what build tools and package managers actually do and why they exist. Once that clicks, every language ecosystem will feel familiar even when the tool names differ.

At the end of this module there is a complete reference project — a real Flask app you can clone, run, test, and build into a Docker image using everything covered here.

What You Will Learn

• Why build tools and package managers exist and what problem each one solves
• How to read and understand build configs across different languages
• How to use Gradle for Java projects and Poetry for Python projects
• How dependencies work, what lock files do, and why they matter
• How to version artifacts properly and why it matters in production
• How to package your app as a Docker image the right way
• How to tie everything together with a Makefile
• How to run a complete build, test, and package workflow yourself

Why This Matters for DevOps Engineers

You write pipeline steps every day. Those steps install dependencies, run tests, build artifacts, and push images. If you do not understand what those steps are actually doing, you cannot fix them when they break — and they will break.

Build and package management is also where most CI/CD problems live. "Works on my machine" almost always traces back to a dependency version mismatch, a build environment difference, or an artifact that was not properly locked.