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.

Is your feature request related to a problem? Please describe.
Hi Team,

Are you planning to release golangci/golangci-lint image for arm64?

Describe the solution you'd like
I am checking on adding arm64 support in Travis-CI for kube-router package, but I was facing issue in pulling golangci-lint image for arm64 as it is not available in the docker hub. I have observed that golangci-lin

Is your feature request related to a problem? Please describe.

Following the guidance of github, many developers are moving to main as their default branch. Saving developers from the very small hindrance of using DEFAULT_BRANCH: main would contribute to smoothing the transition.

Describe the solution you'd like

The default branch should be main. If it does not exist, use `m

@vito

Summary

Backend error: Exit status: 500, message: {"Type":"ExecutableNotFoundError","Message":"OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused \"exec: \\\"bash\\\": executable file not found in $PATH\": unknown","Handle":"","ProcessID":"","Binary":""}

Steps to reproduce

Use @vito buildkit container, or any container which doe

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.

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

Sep	OCT	Nov
	22
2019	2020	2021

ci

Here are 3,036 public repositories matching this topic...

chinese-poetry / chinese-poetry

drone / drone

goldbergyoni / javascript-testing-best-practices

nektos / act

golangci / golangci-lint

gocd / gocd

github / super-linter

adnanh / webhook

concourse / concourse

Summary

Steps to reproduce

postmanlabs / newman

buildbot / buildbot

danger / danger

yonaskolb / XcodeGen

danger / danger-js

xcpretty / xcpretty

ansible-semaphore / semaphore

reviewdog / reviewdog

opendevops-cn / opendevops

ligurio / awesome-ci

GoogleChromeLabs / lighthousebot

tfsec / tfsec

julien-lafont / Mocky

TheLartians / ModernCppStarter

lastbackend / lastbackend

ory / dockertest

zegl / kube-score

harbur / captain

aws-quickstart / taskcat

pycontribs / jenkinsapi

stepchowfun / toast

Essential cookies

Always active

Analytics cookies