This first post will cover the basics of how to connect Jenkins with Github and how to configure both to auto trigger a build upon a pull request (PR) and post back results to GitHub.
While we chose Jenkins and Github, all of the concepts you are going to read here are quite similar between the different tools (bitbucket, TeamCity, GitLab, etc), we only chose Jenkins as it is still being used by most users out there.
Let’s jump right in! Continue reading “Jenkins: building a CI/CD system – part1”
Hello. It’s been ages since my last post, sorry for that. Looks like my work and studies took over most of my time. But let’s not dwell in the past and move to the purpose of this post!
I have quite a lot of interaction with Jenkins lately and to be honest, I really don’t like using the Jenkins web interface. I’m always in favor of using good working CLI.
Unfortunately I couldn’t find any client that was good enough for what I’ve been doing with Jenkins. My requirements are pretty basic – 1. it should work, 2. it should cover enough of the different tasks I’m doing on Jenkins. I have been trying couple of clients, but each was either too basic, missing a lot of commands or either not working at some point.
Continue reading “Jenkins: New CLI”
Sometimes when you submit patch to gerrit, you may have one or several gates running against the patch, verifying it has no issues, so it’s safe to merge it.
But what would you do if want to re-run all gates? usually I see developers using one of the following ways:
- go to the actual build page in jenkins and click on ‘retrigger all’
- comment in gerrit system with specific string
Rebase would work only if there is what to rebase on and using directly the build page on jenkins server will only work if you have account with permissions to access this jenkins server – so those two methods would be less convenient to use.
Continue reading “Jenkins & Gerrit: trigger build on added comment”