AWS CodeBuild vs Jib

AWS CodeBuild is a paid, cloud-hosted continuous integration service for compiling, testing, and packaging code from build scripts. It provisions and scales build capacity automatically, so projects do not require users to manage build servers. Preconfigured environments cover Java, Python, Node.js, Ruby, Go, Android, .NET Core for Linux, and Docker; teams can also supply Docker-based environments. A YAML build specification defines commands for each build phase and other settings. Builds can start from CodeCommit, GitHub, GitHub Enterprise, Bitbucket, Amazon S3, or CodePipeline, and can work with Jenkins. Artifacts can be stored in S3 or sent to an artifact repository. IAM provides access controls, while KMS keys encrypt artifacts. Build timing, status, commit ID, metrics, and logs are available through the service and CloudWatch, with SNS event notifications. A free plan provides stated monthly allowances; paid usage starts at 0.01 USD and can add charges for data transfer and related AWS services.

Jib builds Docker and OCI images for Java applications without a Docker daemon. It can be used as a Maven or Gradle plugin, a Java library, or a command-line interface, and runs on Linux, macOS, and Windows. Jib divides application contents into layers, allowing code changes to be rebuilt without rebuilding the whole image. It can push images to a container registry of the user's choice, uses an OpenJDK base image by default, and accepts a custom base image. The project says that rebuilding an image from the same contents produces the same image. It supports local build caches and multi-architecture builds, and the project says it works well with Google Cloud Build. Examples cover Spring Boot, Micronaut, multi-module projects, and Spark Java with a Java Agent. Jib is free and open source under Apache License, Version 2.0. The project is not an officially supported Google product; it directs usage questions to Stack Overflow and also links to GitHub issues and a FAQ.