Jenkins is an open-source automation server that can run your project’s build and test commands whenever you trigger a pipeline. To use it for continuous integration (CI), install Jenkins, connect a source-control repository, add a Jenkinsfile describing the build and tests, then inspect the run’s status and output.
What Jenkins does in CI
Jenkins automates tasks involved in building, testing, delivering, or deploying software. It coordinates work; it does not replace your project’s test framework. Your pipeline tells Jenkins which commands to run, and those commands invoke the tools and tests your project already uses.
As an Amazon Associate I earn from qualifying purchases.
Jenkins Pipeline is a suite of plugins for defining software delivery workflows as code. A pipeline is organized into stages and steps. The usual practice is to store its definition in a file named Jenkinsfile in the project repository, so changes to the automation can be reviewed and versioned with code changes. See the Pipeline overview.
Set up a basic Jenkins CI workflow
- Choose an installation environment. Jenkins documentation covers Docker, Kubernetes, Linux, macOS, Windows, and a standalone WAR. Follow the instructions for your chosen environment and supported Java version in the Jenkins documentation. Do not assume one Java prerequisite applies to every installation method.
- Complete initial setup and check Pipeline support. Pipeline is a plugin suite. The getting-started guide says it is included among the suggested plugins offered by the setup wizard. Installed plugins determine which pipeline steps are available on your instance; consult the Pipeline getting-started guide.
- Add a Jenkinsfile to the repository. Start with Declarative Pipeline if you want a structured, readable example. Use the commands your project actually runs to build and test locally.
- Connect Jenkins to source control. Create a Pipeline job that loads its definition from source control, or create a Multibranch Pipeline to discover branches containing pipeline definitions. Set the script path to match the file’s location in the repository.
- Run the pipeline and inspect its result. Check the build status and console output. Separate stages such as Build and Test make it easier to see where work succeeded or failed.
The official first Pipeline tour demonstrates repository-based workflows and examples for different project stacks. Jenkins does not prescribe a universal test command: use your own project’s build and test commands.
#1 Best Overall
Write a starter Jenkinsfile
This illustrative Declarative Pipeline runs two shell scripts from the workspace. It is a pattern to adapt, not a claim that the commands have been tested for your project.
pipeline {
agent any
stages {
stage('Build') {
steps {
sh './build.sh'
}
}
stage('Test') {
steps {
sh './test.sh'
}
}
}
}Save the file as Jenkinsfile at the repository path configured in the job. Replace ./build.sh and ./test.sh with commands and scripts that exist in your project. On a Windows agent, use an appropriate Windows command step and Windows-compatible project commands instead of sh.
agent any allows Jenkins to run the pipeline on an available agent. The Jenkins environment still needs the tools and dependencies those commands require. Keep credentials out of source-controlled pipeline text; use Jenkins credential facilities when a workflow needs secrets, following the current Jenkins documentation for the setup appropriate to your instance.
Choose Declarative or Scripted Pipeline
Jenkins supports both formats. Declarative syntax provides a structured way to express stages and steps and is a practical starting point for a simple CI workflow. Scripted Pipeline uses a limited form of Groovy syntax and allows a different style of pipeline definition. Choose the format your team can review and maintain; the official getting-started guide links to syntax references and generators available in Jenkins.
Common setup and pipeline problems
- Jenkins cannot find the Jenkinsfile: Check that the file is committed to the connected repository and that the job’s script path matches its location and capitalization.
- A command works locally but fails in Jenkins: The selected agent may lack a required tool, dependency, environment variable, or working-directory assumption. Review the console output and make the agent environment satisfy the project’s documented build prerequisites.
- The shell step is not appropriate for the agent:
shis for shell commands. Use an appropriate Windows command step on a Windows agent and ensure the script syntax matches that environment. - The run stops during a stage: Read the console output to identify the failed command and stage, then run the same project command in a matching environment. Fix the underlying build or test failure before changing pipeline syntax.
- A pipeline step is unavailable: Pipeline steps depend on plugins installed on that Jenkins instance. Check plugin availability and the relevant step documentation for the instance’s installed plugins.
Installation details depend on the environment
Jenkins can be installed through native packages, Docker, or as a standalone application on a machine with a suitable Java Runtime Environment. Exact steps and supported Java versions depend on the installation method and platform. For example, the Jenkins guided tour’s standalone setup lists Java 21 or 25 and Docker, then launches Jenkins with java -jar jenkins.war --httpPort=8080; those are prerequisites and commands for that tour setup, not universal requirements. Consult the guided tour setup before following it.
Running application tests is different from testing Jenkins
In most CI discussions, “testing with Jenkins” means using Jenkins to run an application’s test suite. Jenkins developers also test Jenkins itself and its plugins. That separate process uses a JUnit-based test harness to set up and tear down Jenkins installations, with helpers for jobs, agents, security realms, and source-control integrations. See the Jenkins developer testing guide.
Rank #4
Or skip the browser setup
For screenshot checks in a CI workflow, ScreenshotNeo is a website screenshot API and MCP server. Make a GET request with the page URL to return a PNG, JPEG, WebP, or PDF. See the API documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie and consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers indicate the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
