From fe7c7eda7ee1db8be715e6aa32430e077ce2d385 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Wed, 15 Apr 2026 20:18:36 +0200 Subject: [PATCH] [bitnami/jenkins] Release 2.555.1-debian-12-r0 (#92496) Signed-off-by: Bitnami Bot --- bitnami/jenkins/2/debian-12/Dockerfile | 10 ++--- bitnami/jenkins/README.md | 56 +++++--------------------- 2 files changed, 14 insertions(+), 52 deletions(-) diff --git a/bitnami/jenkins/2/debian-12/Dockerfile b/bitnami/jenkins/2/debian-12/Dockerfile index 09f841f4fbf4..40366f8da1f0 100644 --- a/bitnami/jenkins/2/debian-12/Dockerfile +++ b/bitnami/jenkins/2/debian-12/Dockerfile @@ -8,13 +8,13 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-04-11T01:39:35Z" \ + org.opencontainers.image.created="2026-04-15T17:58:56Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/jenkins/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/jenkins" \ org.opencontainers.image.title="jenkins" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="2.541.3" + org.opencontainers.image.version="2.555.1" ENV HOME="/" \ OS_ARCH="${TARGETARCH:-amd64}" \ @@ -32,7 +32,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ "nss-wrapper-1.1.16-0-linux-${OS_ARCH}-debian-12" \ "render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \ "jre-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \ - "jenkins-2.541.3-0-linux-${OS_ARCH}-debian-12" \ + "jenkins-2.555.1-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -51,9 +51,9 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true COPY rootfs / RUN /opt/bitnami/scripts/java/postunpack.sh RUN /opt/bitnami/scripts/jenkins/postunpack.sh -ENV APP_VERSION="2.541.3" \ +ENV APP_VERSION="2.555.1" \ BITNAMI_APP_NAME="jenkins" \ - IMAGE_REVISION="3" \ + IMAGE_REVISION="0" \ JAVA_HOME="/opt/bitnami/java" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/java/bin:$PATH" diff --git a/bitnami/jenkins/README.md b/bitnami/jenkins/README.md index e992eaf84253..bad25dd455a1 100644 --- a/bitnami/jenkins/README.md +++ b/bitnami/jenkins/README.md @@ -13,6 +13,14 @@ docker run --name jenkins bitnami/jenkins:latest You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section. +## Using `docker-compose.yml` + +The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/). + +[https://github.com/bitnami/containers/tree/main/bitnami/jenkins/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/jenkins/docker-compose.yml) + +Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/jenkins). + ## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -121,8 +129,6 @@ The following tables list the main variables you can set. | `JENKINS_DEFAULT_HTTPS_PORT_NUMBER` | Default Jenkins HTTPS port number to enable at build time. | `8443` | | `JENKINS_DEFAULT_JNLP_PORT_NUMBER` | Default Jenkins JNLP port number to enable at build time. | `50000` | -When you start the Jenkins image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. - ### FIPS configuration in Bitnami Secure Images The Bitnami Jenkins Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: @@ -132,51 +138,7 @@ The Bitnami Jenkins Docker image from the [Bitnami Secure Images](https://go-vmw ## Logging -The Bitnami Jenkins Docker image sends the container logs to `stdout`. To view the logs: - -```console -docker logs jenkins -``` - -Or using Docker Compose: - -```console -docker-compose logs jenkins -``` - -You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. - -## Maintenance - -### Backing up your container - -To backup your data, configuration and logs, follow these simple steps: - -#### Step 1: Stop the currently running container - -- For docker-compose: `$ docker-compose stop jenkins` -- For manual execution: `$ docker stop jenkins` - -#### Step 2: Run the backup command - -We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data. - -```console -docker run --rm -v /path/to/jenkins-backups:/backups --volumes-from jenkins bitnami/os-shell \ - cp -a /bitnami/jenkins /backups/latest -``` - -### Restoring a backup - -Restoring a backup is as simple as mounting the backup as volumes in the containers. - -```diff - $ docker run -d --name jenkins \ - ... -- --volume /path/to/jenkins-persistence:/bitnami/jenkins \ -+ --volume /path/to/jenkins-backups/latest:/bitnami/jenkins \ - bitnami/jenkins:latest -``` +The Bitnami Jenkins Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver. ## Customize this image