Skip to content
#

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,894 public repositories matching this topic...

golangci-lint
DarthHater
DarthHater commented Aug 18, 2020

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 using latest on your Docker image tag, I'd suggest using v0.3 or v0 for now, and then moving back to latest once you've had some time to digest the changes.

Mocky
moniuch
moniuch commented Apr 25, 2017

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

Wikipedia
Wikipedia
You can’t perform that action at this time.