Difficulty: Intermedia
Estimated Time: 15-20 minutes

En este escenario, aprenderá a configurar Jenkins integrado con Gitlab y Selenium.

El escenario está diseñado para demostrar cómo se pueden utilizar diferentes herramientas dentro de un Pipeline de integración continua, utilizando las imágenes como un artefacto de construcción que se puede promover a diferentes entornos y finalmente la producción. Los pasos le guían para instalar el plugin, crear una compilación y ver los resultados.

This scenario took a new Jenkins build and configured it to build Docker Images. We then look an example HTTP server and created a build for it.

Learn how to launch a Private Docker Registry with our scenario.

Don’t stop now! The next scenario will only take about 10 minutes to complete.

Integración continua I

Step 1 of 6

Ejecutar Jenkins

The environment has a Jenkins server running as a Docker Container. You can view the status using docker ps.

The command used to launch the container was:

docker run -d -u root --name jenkins \ -p 8080:8080 -p 50000:50000 \ -v /root/jenkins:/var/jenkins_home \ jenkins:1.651.1-alpine

All plugins and configurations get persisted to the host at /root/jenkins. Port 8080 opens the web dashboard, 50000 is used to communicate with other Jenkins agents. Finally, the image has an alpine base to reduce the size footprint.

Load Dashboard

You can load the Jenkins' dashboard via the following URL https://[[HOST_SUBDOMAIN]]-8080-[[KATACODA_HOST]].environments.katacoda.com/

In the next steps, you'll use the dashboard to configure the plugins and start building Docker Images.