Jenkins

“More than 10 years of running my own CI infra with Jenkins on top. In 2023 I gave up Jenkins and paid for BuildKite.”

“we run a Jenkins instance for our platform that has bi-weekly production releases.”

“lacking support meant little things like Jenkins having to pull 3x instead of 1x for git natively”

“I wrote several custom tools in Python, and we used Jenkins as our CI/CD server.”

“Jenkins pipeline wise very similar - land on main, will go in the next nightly build.”

“We automate all this with a jenkins pipeline.”

“the funny part was that we run all this thing via Jenkins & bash.”

“we've used from before we migrated from Jenkins to GitHub actions”

“Keycloak for OAuth, Jenkins for CI/CD”

“At my company, we run our CI/CD (Jenkins) using the Docker-in-Docker paradigm”

“We execute Liquibase using Jenkins.”

“We use Jenkins now and build for PCs, consoles, and mobile.”

“there's a Jenkins Mask Passwords plugin which we use in conjunction with not exposing our Jenkins server to the Internet”

“Deployment to the production is done through Jenkins.”

“The integration into our Jenkins instance was a complete nightmare”

“you have to make at least 3 changes: the actual code update, the packer script, and your Jenkins worker”

“Jenkins will spin up ~50 concurrent EC2 instances running docker, run the tests, and report back”

“There's also a couple of Jenkins servers.”

“Instead of a Zookeeper scheduler, it's just Jenkins.”

“We run our builds within containers (using the Jenkins k8s plugin) for repeatability”

“We use a Gitea for source control and Jenkins for CI.”

“We run bunch of groovy startup scripts that configure everything post launch.”

“We self host JIRA, Jenkins, our own backoffice and other stuff on a small instance.”

“You can build all of what I mentioned with OSS like: Ansible (deployment) Jenkins (ci) ELK stack (metrics / logging) Zabbix (system metrics)”

“On commits, we run the lightweight CI in Jenkins. What I mean by lightweight is that, there's only a few runners”

“I'd need to do some SSH into the Jenkins server, so you run only your brand new integration test.”

“We just killed our last Jenkins instance last week after we found out that everyone eventually moved to the GitLab CI.”

“It integrates so well with our Gitlab/Jenkins flow, too.”

“Juenkins' Kubernetes plugin allows to mount secrets like with usual pods so we deploy test secrets just like we normally do production ones.”

“It stays disabled in our jenkins.”

“our Docker container building (Jenkins + custom Groovy), our monitoring (Datadog-based)”

“We run Bitbucket at my company and Jenkins Enterprise as well.”

“The biggest issue we see at Yelp is leaking containers in test (e.g. Jenkins aborting a job but leaving the containers it spawned still running).”

“Jenkins is also a first class stage type - it is the way we run the build and test side of our deployments”

“Combined with Jenkins, makes it easy to make sure your master branch is in a good state.”

“we have a self-hosted Jenkins instance and have looked as hosted alternatives.”

“Like many others we run Jenkins to handle our build and deployment.”

“To clarify, we run github freshdesk and jenkins integrations.”

“Yes, we run pronto when our Jenkins builds GitHub pull requests, so we get all those comments along with peer code reviews.”

“We would review the code manually, and later also used tools such as Jenkins and Sonar.”

“We run some of our jenkins build slaves on OVH.”

“is the reason I know maven, ant, chef AND puppet, Jenkins, and gradle as well as I do.”

“we've been using this CI server for many months now. We started out with Hudson, but after observing the unethical shenanigans from Oracle”