Installing Jenkins Blue Ocean and Creating Pipelines (Classic and Blue Ocean Modes)

The article begins by recommending Docker for installing Jenkins Blue Ocean to avoid Java environment issues. It shows three commands: pulling the jenkinsci/blueocean image, creating a /var/jenkins_home directory, and running the container with ports 8888, 8080, and 50000 mapped.

After logging into Jenkins, the UI displays the Blue Ocean icon. Users can install the Blue Ocean plugin via Manage Jenkins → Manage Plugins if using the standard Jenkins distribution.

Classic mode pipeline creation is described step‑by‑step: create a new job, select Pipeline , configure the General section (name, description, GitHub project), set Build Triggers (e.g., SCM polling), and define the pipeline script.

The pipeline uses a Declarative syntax with stages such as Build , Docker Build , Deploy , and Test . An example Jenkinsfile is provided, showing agents, environment variables, stages, steps (shell commands, Git checkout, Docker commands, artifact archiving), and credential usage.

Key concepts such as Agent , Stage , and Step are explained, and the article notes that artifacts (e.g., APKs, Docker images) should be archived for later download.

Blue Ocean mode offers a visual pipeline editor. After opening Blue Ocean, users click “Create new pipeline”, select a repository, provide credentials, and let Jenkins generate a Jenkinsfile automatically. The generated file mirrors the manually written one and is stored in the code repository.

The article concludes by comparing the two approaches: classic mode offers full control for complex pipelines, while Blue Ocean provides a low‑code, beginner‑friendly way to create pipelines quickly.