Skip to content

Commit

Permalink
chore: cleaning comment and rewording
Browse files Browse the repository at this point in the history
Signed-off-by: Olblak <[email protected]>
  • Loading branch information
olblak committed Dec 20, 2024
1 parent 6cc503e commit a4e3783
Showing 1 changed file with 7 additions and 29 deletions.
36 changes: 7 additions & 29 deletions content/en/docs/guides/dockerfile.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ toc: true

This guide analyzes how the Jenkins project automates its Dockerfile file updates.

It's one thing to publish a Docker image, but it's another one to maintain it over time, like the Jenkins project does.
It's one thing to publish a Docker image, but it's another one to maintain it over time.

To scope this guide, we focus on monitoring Java version, and more precisely Java 17.

Expand Down Expand Up @@ -64,31 +64,9 @@ The pipeline we are analyzing could be schematized as follows:

image::/images/diagrams/guide-dockerfile.svg[]

// https://gohugo.io/content-management/diagrams/#mermaid-diagrams
//```mermaid
//graph TD
// condition#checkTemurinAllReleases{"Check if the #quot;lastVersion#quot; is available for all platforms (temurin)"}
// condition#checkTemurinAllReleases --> target#setJDK17VersionAlpine
// target#setJDK17VersionAlpine("Bump JDK17 version for Linux images in the Alpine Linux Dockerfile (dockerfile)")
// condition#checkTemurinAllReleases --> target#setJDK17VersionDebian
// target#setJDK17VersionDebian("Bump JDK17 version for Linux images in the Debian Dockerfiles (dockerfile)")
// condition#checkTemurinAllReleases --> target#setJDK17VersionRhel
// target#setJDK17VersionRhel("Bump JDK17 version for Linux images in the Rhel Dockerfile (dockerfile)")
// condition#checkTemurinAllReleases --> target#setJDK17VersionWindowsDockerImage
// target#setJDK17VersionWindowsDockerImage("Bump default JDK17 version for Linux images in the Windows Dockerfile (dockerfile)")
// condition#checkTemurinAllReleases --> target#setJDK17VersionDockerBake
// target#setJDK17VersionDockerBake("Bump JDK17 version for Linux images in the docker-bake.hcl file (hcl)")
// condition#checkTemurinAllReleases --> target#setJDK17VersionWindowsDockerCompose
// target#setJDK17VersionWindowsDockerCompose("Bump JDK17 version in build-windows.yaml (yaml)")
// source#lastVersion(["Get the latest Adoptium JDK17 version (temurin)"])
// source#lastVersion --> target#setJDK17VersionDebian
// source#lastVersion --> condition#checkTemurinAllReleases
// source#lastVersion --> target#setJDK17VersionRhel
// source#lastVersion --> target#setJDK17VersionWindowsDockerImage
// source#lastVersion --> target#setJDK17VersionDockerBake
// source#lastVersion --> target#setJDK17VersionWindowsDockerCompose
// source#lastVersion --> target#setJDK17VersionAlpine
//```
The schema was generated using the following command:

* `updatecli manifest show --config updatecli.d/manifest.yaml --values updatecli/values.yaml --experimental --graph --graph-flavor=mermaid`

==== Manifest

Expand Down Expand Up @@ -137,9 +115,9 @@ This manifest named `Bump JDK17 version` can be split into five sections:
====
[source,yaml]
----
scms:
default:
kind: github
It’s one thing to publish a Docker image, but it’s another one to maintain it over time, like the Jenkins project does.
spec:
user: "{{ .github.user }}"
email: "{{ .github.email }}"
Expand Down

0 comments on commit a4e3783

Please sign in to comment.