Search Results for "cd"

Built on the simple mechanics of resources, tasks, and jobs, Concourse presents a general approach to automation that makes it great for CI/CD. Concourse is designed to be expressive, versatile, and safe, remaining intuitive as the complexity of your project grows. A Concourse pipeline is like a distributed, continuous Makefile. Each job has a build plan declaring the job's input resources and what to run with them when they change. Your pipeline is then visualized in the web UI, taking only one click to get from a failed job to seeing why it failed. ...

GC Build official builder images is a repository that provides a collection of prebuilt and customizable container images used with Google Cloud Build to automate CI/CD pipelines. These builder images act as modular steps within build pipelines, allowing developers to perform tasks such as compiling code, running tests, building Docker images, and deploying applications. The repository includes a wide range of builders for different languages, tools, and workflows, enabling flexible and extensible pipeline design. ...

Drone is a self-service Continuous Integration platform for busy development teams. Pipelines are configured with a simple, easy‑to‑read file that you commit to your git repository. Each Pipeline step is executed inside an isolated Docker container that is automatically downloaded at runtime. Drone integrates seamlessly with multiple source code management systems, including GitHub, GitHubEnterprise, Bitbucket, and GitLab. Drone natively supports multiple operating systems and architectures,...

...It's ideal for use cases where your image contains a single Go application without any/many dependencies on the OS base image (e.g., no cgo, no OS package dependencies). ko builds images by effectively executing go build on your local machine, and as such doesn't require docker to be installed. This can make it a good fit for lightweight CI/CD use cases. ko also includes support for simple YAML templating which makes it a powerful tool for Kubernetes applications. ko depends on the authentication configured in your Docker config. If you can push an image with docker push, you are already authenticated for ko. Since ko doesn't require docker, ko login also provides a surface for logging in to a container image registry with a username and password, similar to docker login. ...

...Building once is painful enough, Turborepo will remember what you've built and skip the stuff that's already been computed. Turborepo looks at the contents of your files, not timestamps to figure out what needs to be built. Share a remote build cache with your teammates and CI/CD for even faster builds. Speed up PaaS deploys by generating a subset of your monorepo with only what's needed to build a specific target. Turborepo won’t interfere with your runtime code or touch your sourcemaps. Execute builds using every core at maximum parallelism without wasting idle CPUs. Define the relationships between your tasks and then let Turborepo optimize what to build and when.