a high-level container image build tool
-
Updated
May 12, 2023 - Go
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
Continuous delivery contrasts with continuous deployment (also abbreviated CD), a similar approach in which software is also produced in short cycles but through automated deployments even to production rather than requiring a "click of a button" for that last step. As such, continuous deployment can be viewed as a more complete form of automation than continuous delivery.
a high-level container image build tool
Golang project CI/CD in gitlab and deploy K8s
Automatic semantic versioning utility
A simple webhook API to run system commands or scripts. Great for triggering deployments or other Linux operational tasks.
Easily update your kubernetes images FROM WITHIN
Keep Kubernetes Deployments up-to-date with the `latest` container images
Simple deployer server
Pause a GitHub Actions workflow and wait for another workflow to complete before continuing.
Easier CI/CD on Kubernetes using GitHooks
A Terraform provider for https://prodvana.io
Standardized CLI
Simple GitHub Action that redeploys Render applications
neoCargo microservices in Go with PostgreSQL, MongoDB, Terraform, Google Kubernetes Engine, and CircleCI
🏯 Monitor your (gitlab/github) CI/CD pipelines via command line interface with fortress
Terraform provider for Buildkite
Building Microservices with Go by Nic Jackson
DevCycle - SDK Proxy
Release auditing & approval platform
Packer post-processor plugin to upload artifacts to Vagrant Cloud from the input filepath (without a requirement of using 'vagrant' post-processor). Useful to split Packer build/deploy stage.