Search Results for "rules"

...GitHub, GitLab, Gitea, custom Git repositories (and more to come). Execute your tasks inside a Kubernetes cluster, local docker, etc. Keep the same Runs definition but use different variables values based on rules to test your runs on multiple environments. Runs definitions are committed inside your git repositories and triggered upon push/tag/pull request. Scalable and High Available: go from a single instance (single process) deployment to a distributed deployment. Deploy anywhere: Kubernetes, IaaS, bare metal and execute the "tasks" anywhere (currently containers executors like docker or orchestrators and Kubernetes, but easily extensible to future technologies or VMs instead of containers). ...

werf is an Open Source CLI tool written in Go, designed to simplify and speed up the delivery of applications. To use it, you need to describe the configuration of your application (in other words, how to build and deploy it to Kubernetes) and store it in a Git repo, the latter acts as a single source of truth. In short, that's what we call GitOps today. werf is not a complete CI/CD solution, but a tool for creating pipelines that can be embedded into any existing CI/CD system. It literally...

bors-ng is a GitHub merge bot that enforces an “evergreen” main branch by queueing approved pull requests, testing them together on a staging branch, and only advancing main with the exact, passing commit set. Instead of maintainers repeatedly rebasing and merging one PR at a time, bors-ng batches r+-ed PRs, triggers your existing CI (e.g., GitHub Actions), and merges automatically when the batch is green. If a batch fails, it bisects the batch into smaller runs to isolate the culprit,...

...Can be integrated with code hosting platforms such as Gitlab, Github, Gogs, Gitee (Oschina). Flexibility to configure custom build and deployment steps. Support for custom build rules, create releases and deploy builds. Support multi-environment deployment of the project (you can create multiple environments such as development, testing, pre-release and production by yourself). Support linkage deployment, for example: after the development environment is successfully deployed, the test environment can be automatically triggered to start the deployment.