Jenkins mostly just keeps the CI lights on for our UI automation, which is honestly what I need most days. We host it on a Linux server and it’s rock-solid: pipelines fire when they should, and the connection to our Selenium Grid on remote Windows 11 machines is seamless enough that I barely think about it. I kick off a job, agents spin up, tests run, reports land—done, no drama. The plugin ecosystem is a big win too: test reporters, HTML publisher, Slack and email notifications, credentials bindings, all the usual suspects. That makes it easy to wire up a pipeline that matches our workflow without bolting on a bunch of custom glue. Once the Jenkinsfile is in place, everything feels predictable run after run; the logs are clear enough, and failures usually point to the right stage so I can fix things and move on.
Day-to-day usage is pretty straightforward. We schedule weekly runs across different environments, pass parameters for browser or env, and the matrix job handles it cleanly without me babysitting every combo. Branch builds are easy, artifacts get archived, and test results show up in the job with trends so we can spot regressions fast instead of guessing. Git integration is simple enough too: webhooks trigger CI, the job picks up the latest commit, and there are no manual steps or copy-paste. Labels help isolate jobs so Windows grid work stays separate from other tasks, and the Linux master stays calm even when the queue gets busy. Folders and role-based access provide decent guardrails, secrets live in the credentials store so people don’t stash tokens in scripts, and shared library functions keep our pipeline steps consistent across repos, which cuts down the chaos a lot.
Support and docs are decent, and the community answers usually get me unstuck when I hit an odd edge case—often after a plugin update. It’s not perfect: plugins can be picky, a node will go offline now and then, and sometimes a flaky test makes a stage look worse than it is. Still, the feedback loop is fast and reliable. The net result is simple: faster iteration, fewer setup headaches, and cleaner commits that flow right into our ADO repo and CI without me babysitting a bunch of steps. It keeps the work organized and predictable, which is exactly what I need for UI automation, and it saves me a lot of little minutes across the week so I can focus on fixing issues instead of wrangling the pipeline. Review collected by and hosted on G2.com.
The initial setup was the only part that felt genuinely tricky. We spent quite a bit of time going back and forth with DevOps to land on the right configurations, plugins, agent permissions, and service accounts. Once that was sorted out, everything has been smooth sailing.
Every so often, the Selenium Grid goes down, but that’s tied to our remote machines rather than Jenkins itself—usually a restart on the Windows side brings it right back. Plugin updates can also be a little touchy at times: dependencies get bumped and then a job starts complaining, but a quick rollback or a small reconfiguration typically resolves it. None of this is a dealbreaker; they’re just minor bumps you notice more when deadlines are tight. Review collected by and hosted on G2.com.
Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
Invitation from G2. This reviewer was not provided any incentive by G2 for completing this review.
