Search Results for "local software alternatives"

When you run Act it reads in your GitHub Actions and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files, and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The environment variables and filesystem are all configured to match...

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...

Execute your runs in a reproducible containerized environment. Restart them from start or from the failed tasks. Implement every kind of workflow you want from simple builds to complex deployments. 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...

Captain - Convert your Git workflow to Docker containers ready for Continuous Delivery. Define your workflow in the captain.yaml and use captain to your Continuous Delivery service to create containers for each commit, test them and push them to your registry only when tests passes. Use captain build to build your Dockerfile(s) of your repository. If your repository has local changes the containers will only be tagged as latest, otherwise the containers will be tagged as latest, COMMIT_ID &...