ci
Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.
Here are 2,885 public repositories matching this topic...
Drone is a Container-Native, Continuous Delivery Platform
-
Updated
Aug 19, 2020 - Go
Main repository for GoCD - Continuous Delivery server
-
Updated
Aug 25, 2020 - Java
Fix GO linting
When viewing a build that reconfigures pipelines, it's hard to tell which pipelines were actually changed:
Quick suggestion: highlight it in yellow, like the get step? Or the opposite - dim steps which had no changes to apply? No strong preference!
This would likely involve emittin
Newman is a command-line collection runner for Postman
-
Updated
Aug 23, 2020 - JavaScript
JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.
http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.
-
Updated
Aug 25, 2020 - Ruby
A Swift command line tool for generating your Xcode project
-
Updated
Aug 25, 2020 - Swift
-
Updated
Aug 19, 2020 - TypeScript
-
Updated
Aug 25, 2020 - Go
Run Lighthouse in CI, as a web service, using Docker. Pass/Fail GH pull requests.
-
Updated
Jul 7, 2020 - JavaScript
List of Continuous Integration services
-
Updated
Aug 12, 2020
Hi, great project. I'd like to make a request. Right now, to exclude rules, you have to modify the code to "a comment containing tfsec:ignore:<RULE> to the offending line in your templates", per the README. It would be very useful if we could do this via CLI args as well, for assessment purposes.
I would welcome a feature when, at the same url which is set to respond with OK status, I could have an error response generated with a random seed.
I am developing an Observable pattern to perform a series of retries to call an endpoint, with increasing delay. The problem is that during testing, I cannot really mock up the condition by randomly switching between two mocky.io urls (error and ok
System for containerized apps management. From build to scaling.
-
Updated
Aug 6, 2020 - Go
Kick-start your C++! A template for modern C++ projects using CMake, CI, code coverage, clang-format, reproducible dependency management and much more.
-
Updated
Aug 20, 2020 - CMake
Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
-
Updated
Aug 10, 2020 - Go
Kubernetes object analysis with recommendations for improved reliability and security
-
Updated
Aug 23, 2020 - Go
Captain - Convert your Git workflow to Docker
-
Updated
Oct 17, 2019 - Go
A Python API for accessing resources and configuring Hudson & Jenkins continuous-integration servers
-
Updated
Jul 9, 2020 - Python
Containerize your development and continuous integration environments.
-
Updated
Aug 4, 2020 - Rust
Test all the CloudFormation things! (with TaskCat)
-
Updated
Aug 11, 2020 - Python
Ansible Role - Jenkins CI
-
Updated
Aug 21, 2020 - Groovy
- Wikipedia
- Wikipedia



Hello!
We saw you are using
nancy, and we are humbled! I thought I'd reach out and let you know that we will have a 1.0.0 release coming soon, and usage is going to change slightly. To avoid disruption to your project, rather than usinglateston your Docker image tag, I'd suggest usingv0.3orv0for now, and then moving back tolatestonce you've had some time to digest the changes.