CI/CD & build tooling
Build tools & artifact repositories
Build tools and artifact repositories sit between source code and the container image. Senior DevOps interviews ask how Maven and Gradle actually resolve and build, why builds are slow or non-reproducible, how versions and SNAPSHOTs work, how Nexus/Artifactory/CodeArtifact proxy and host artifacts, and how you'd design an artifact flow that is fast, auditable and secure. This topic also covers the other ecosystems you'll meet (npm, pip, Go) at the level a platform engineer needs.
After this topic you can
- Explain how Maven, Gradle and npm builds work
- Version and publish artifacts to a repository
- Make builds fast, reproducible and cache-friendly
Lessons
-
1Why build tools and artifact management matter
- The flow from commit to deployable
- Build once, promote everywhere
-
2Maven in depth
- Coordinates and the POM
- Lifecycle, phases and goals
- Dependency scopes
- Transitive dependencies and conflicts
- Multi-module builds
- SNAPSHOT vs release
- settings.xml and mirrors
-
3Gradle in depth
- The model
- Dependency configurations
- Why Gradle is fast
- The Gradle wrapper
- Publishing
- Maven vs Gradle
-
4Artifact repositories: Nexus, Artifactory, CodeArtifact
- Repository types
- Products
- Retention and cleanup
- High availability and backup
-
5Versioning, reproducibility and supply chain
- Semantic versioning
- Reproducible builds
- Supply chain security
- 6Other ecosystems a platform engineer meets
-
7Builds inside containers and CI
- Multi-stage Dockerfile for a Java service
- Choices in CI
- 8Troubleshooting builds
-
9Interview questions and model answers
- "Explain the Maven lifecycle. What's the difference between install and deploy?"
- "SNAPSHOT vs release versions?"
- "How does Maven resolve version conflicts, and how do you fix one?"
- "Why is Gradle faster than Maven?"
- "Why put Nexus or Artifactory in front of Maven Central?"
- "How do you make builds reproducible?"
- "How would you use CodeArtifact with GitHub Actions?"