Construindo uma Esteira de CI/CD: Do Código ao Deploy

You containerized the app, isolated the artifact, locked down the credentials and caged the code. But your deploy still depends on you being awake with a terminal open. That's not infrastructure. That's manual process dressed up as architecture. In this video, we rip your hands off the deploy process for good. We build a relentless CI/CD pipeline from absolute zero: Spring Boot API with Java 21, packaged via Multistage Build, versioned on GitHub and automatically deployed to the cloud via GitHub Actions — without you touching a single production terminal. You'll learn how to structure a professional pipeline in workflow.yaml. We'll configure the Gradle cache to cut build time in half, implement a dual image versioning system with latest and a cryptographic commit hash for surgical rollback, and plug Docker Hub in as a sealed artifact vault inside the pipeline. At the end of the line, the production server has exactly one responsibility: pull the image and spin up the container. Zero contact with source code in production. Next episode: The pipeline is up. Now the application needs state. We'll replace the health check with a real CRUD connected to PostgreSQL and wire in the first observability layer with Prometheus and Grafana. Production servers don't guess where the bottleneck is. Recommended in this video If you want to understand what's happening underneath the database you just connected, this one is mandatory: NullDB — Building a relational database engine from scratch:    • Construí um Banco de Dados Sem Usar NENHUM...   Full Docker playlist:    • Docker: Do Absoluto Zero à Arquitetura DevOps   MY SETUP (LAB): Machine: Acer Nitro V15 GPU: NVIDIA RTX 3050 Host OS: Pop!_OS VM (Tutorial): Linux Mint 22 (via VirtualBox 7) BUSINESS CONTACT: [email protected] 0:00 - Intro: Manual deploy is amateur work 0:25 - Pipeline architecture: from code to production server 1:02 - Building the Spring Boot API with Java 21 and Gradle 2:11 - Health Check Controller, @RestController and @RequestMapping 3:08 - ResponseEntity and contract with Java Record 4:38 - Validating the API running locally 5:12 - Dockerfile with Multistage Build (JDK on build, JRE on production) 6:13 - Docker Compose, environment variables and production profile 6:53 - Local container build and validation 7:53 - Repository structure: .github/workflows folder 8:04 - Writing pipeline.yaml from scratch 9:01 - Pipeline steps: checkout, JDK 21, Gradle cache and permissions 10:26 - Docker Hub authentication without hardcoded credentials 11:09 - Build and push with dual versioning: latest + commit hash 12:06 - Creating the GitHub repository 13:14 - git init, branch main and first push 13:56 - Pipeline triggered: watching GitHub Actions run in real time 14:35 - Configuring infrastructure secrets on GitHub 16:03 - Rerun, green pipeline and image published on Docker Hub 17:05 - Deploy on Render: pulling the image straight from the registry 18:37 - API responding in production on the internet 19:00 - Next steps: Postgres, Prometheus and Grafana #GitHubActions #Docker #SpringBoot #Java21 #CICD #DevOps #Backend #SoftwareEngineering #SoftwareArchitecture #MultiStageBuild #NullPointer