[bitnami/jenkins] Release 2.387.3-debian-11-r3 (#33678)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-05-12 18:42:38 +01:00
committed by GitHub
parent 949b11058b
commit aef3860214
5 changed files with 10 additions and 13 deletions

View File

@@ -4,10 +4,10 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-05-09T16:29:08Z" \
org.opencontainers.image.created="2023-05-12T17:10:54Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2.387.3-debian-11-r2" \
org.opencontainers.image.ref.name="2.387.3-debian-11-r3" \
org.opencontainers.image.title="jenkins" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="2.387.3"

View File

@@ -421,7 +421,7 @@ generate_random_string() {
alphanumeric+special|special+alphanumeric)
# Limit variety of special characters, so there is a higher chance of containing more alphanumeric characters
# Special characters are harder to write, and it could impact the overall UX if most passwords are too complex
filter='a-zA-Z0-9!@#$%^'
filter='a-zA-Z0-9:@.,/+!='
;;
*)
echo "Invalid type ${type}" >&2

View File

@@ -42,12 +42,12 @@ jenkins_env_vars=(
JENKINS_ENABLE_SWARM
JENKINS_CERTS_DIR
JENKINS_KEYSTORE_PASSWORD
JENKINS_OPTS
JENKINS_USERNAME
JENKINS_PASSWORD
JENKINS_EMAIL
JENKINS_SWARM_USERNAME
JENKINS_SWARM_PASSWORD
JENKINS_OPTS
JAVA_HOME
JAVA_OPTS
DISABLE_JENKINS_INITIALIZATION
@@ -108,6 +108,7 @@ export JENKINS_SKIP_BOOTSTRAP="${JENKINS_SKIP_BOOTSTRAP:-no}" # only used during
export JENKINS_ENABLE_SWARM="${JENKINS_ENABLE_SWARM:-no}"
export JENKINS_CERTS_DIR="${JENKINS_CERTS_DIR:-${JENKINS_HOME}}"
export JENKINS_KEYSTORE_PASSWORD="${JENKINS_KEYSTORE_PASSWORD:-bitnami}"
export JENKINS_OPTS="${JENKINS_OPTS:-}"
# Jenkins credentials
export JENKINS_USERNAME="${JENKINS_USERNAME:-user}" # only used during the first initialization
@@ -116,9 +117,6 @@ export JENKINS_EMAIL="${JENKINS_EMAIL:-user@example.com}" # only used during the
export JENKINS_SWARM_USERNAME="${JENKINS_SWARM_USERNAME:-swarm}" # only used during the first initialization
export JENKINS_SWARM_PASSWORD="${JENKINS_SWARM_PASSWORD:-}" # only used during the first initialization
# Jenkins launcher parameters
export JENKINS_OPTS="${JENKINS_OPTS:-}"
# Java configuration
export JAVA_HOME="${JAVA_HOME:-${BITNAMI_ROOT_DIR}/java}"
export JAVA_OPTS="${JAVA_OPTS:-}"

View File

@@ -19,6 +19,7 @@ if [[ -n "${JAVA_OPTS:-}" ]]; then
read -r -a java_opts <<<"$JAVA_OPTS"
args+=("${java_opts[@]}")
fi
args+=("-Duser.home=${JENKINS_HOME}" "-jar" "${JENKINS_BASE_DIR}/jenkins.war")
if is_boolean_yes "$JENKINS_FORCE_HTTPS"; then
args+=(

View File

@@ -25,6 +25,8 @@ You can find the default credentials and available configuration options in the
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released on a regular basis with the latest distribution packages available.
Looking to use Jenkins in production? Try [VMware Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
## How to deploy Jenkins in Kubernetes?
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Jenkins Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/jenkins).
@@ -188,10 +190,6 @@ Available environment variables:
* `JAVA_OPTS`: Customize JVM parameters. No defaults.
#### JENKINS configuration
* `JENKINS_OPTS`: Customize Jenkins launcher parameters. No defaults.
## Logging
The Bitnami Jenkins Docker image sends the container logs to `stdout`. To view the logs:
@@ -322,9 +320,9 @@ docker run -d --name jenkins -p 80:8080 \
bitnami/jenkins:latest
```
### Configuring reverse proxy
### Using custom launcher parameters
If you need to install Jenkins behind a reverse proxy with a prefix, such as mycompany.com/jenkins, you can use the "JENKINS_OPTS" environment variable for this purpose:
In order to use custom parameters for Jenkins launcher, for example if you need to install Jenkins behind a reverse proxy with a prefix such as mycompany.com/jenkins, you can use the "JENKINS_OPTS" environment variable:
```console
docker run -d --name jenkins -p 8080:8080 \