CoreMedia Build Image

This repository provides an image with the required tools to build CoreMedia Content Cloud 12, 11, 10, CoreMedia CMS-9, and CoreMedia Live Context 3 workspaces for use with podman, Docker, and similar systems. Supported platform versions range from 17nm to 23nm.

Images started to be available for AMD64/x86_64 and ARM64/Aarch64 with CMCC-11.

Ready to use examples for some CI environments are also included. They are meant for unchanged integration with platform workspaces in their state without any customizations. Thus they should form a good starting point for real world projects.

The home for the sources to create the image lives at Codeberg with mirrors at GitHub and GitLab.

Feedback

Please use the issues section of this repository at GitHub for feedback.

Goals

This image is intended for use in container based CI systems like Forgejo Actions, GitLab CI, or GitHub Actions. Example starting points are included with this repository, which work within the bounds of the public shared runner limitations.

Also, some common tools for additional preparation steps are included like

• git
• gnupg
• cosign
• openssh

and some compression tools.

We like to support different hardware architectures where appropriate.

Availability

This image can be used via the canonical name provocon/coremedia-build. The tag latest should be expected to be usable for the latest release by CoreMedia.

Tags are named after the first release where the implemented changes are required. Thus, 1801 e.g. can be used for releases cms-9-1801 and onwards. 1904 is the last release intended for CMS-9 and LiveContext 3. 1907 was the first release for CMCC-10, which can be used at least up to CMCC-10-2004 and so on.

• 2110 is the current release to work with CMCC-10.
• 2307 is the current release to work with CMCC-11.
• 2406 is the current release to work with CMCC-12.

The latest Tag works with - at least again - CMCC-12-2406.0.

Unpublished, daily builds are available from the Codeberg, GitHub and GitLab project registries.

Usage

See the examples/ directory with usage examples and don't forget the Maven and NPM registry setup.

Examples for builds with Forgejo Actions, GitLab CI and GitHub Actions will need the additional files in examples/workspace-configuration and a personal Token für pnpm login needs to be created, e.g. through npm-registry-login.sh.

Perhaps you still need to mind some parameters when building CoreMedia Content Cloud, e.g.

mvn install -Dwebdriver.chrome.driver=/usr/bin/chromedriver -Dwebdriver.chrome.verboseLogging=true -DjooUnitWebDriverBrowserArguments=--no-sandbox,--disable-dev-shm-usage

So, with Forgejo Actions, GitLab CI, or GitHub Actions the steps are

Adding files

• workspace-configuration/maven-settings.xml
• workspace-configuration/npm-registry-login.sh

Forgejo Actions:

• .forgejo/workflows/build.yml

GitHub Actions:

• .github/workflows/build.yml

GitLab CI:

• .gitlab-ci.yml

Adding secrets

These values have to be added as CI variables for GitLab CI and as action secrets for Forgejo Actions and GitHub Actions respectively.

CoreMedia Maven Artifacts Repository User and Password:

• CM_MAVEN_USER
• CM_MAVEN_PASSWORD

CoreMedia NPM Registry Token:

• NPMRC_TOKEN

The npmrcraw data can be obtained by using the login script provided in the workspace-configuration folder as indicated above. You will need to update this value every few months.

Optionally add Maven Options

• MAVEN_OPTS

and use Docker Hub login to extend the download rate.

• DH_REGISTRY_USER
• DH_REGISTRY_PASSWORD

Build

Manual Build

The preparation of the container is accomplished using the usual

docker build -t <myname> .

So, for the current version, this is

docker build -t provocon/coremedia-build:2406.0 .
docker build -t provocon/coremedia-build:2406 .
docker build -t provocon/coremedia-build:latest .

docker push provocon/coremedia-build:2406.0
docker push provocon/coremedia-build:2406
docker push provocon/coremedia-build:latest

You could as well use podman instead of docker in each of the lines.

Scripted Build

Alternatively, you could use the Gradle Build Tool and issue

./gradlew -Ptag=2406.0 dockerPush
./gradlew -Ptag=2406   dockerPush
./gradlew -Ptag=latest dockerPush

which does all the steps above for you.

Test

Test the generated resulting container with

$ docker run --name docker --rm -it --entrypoint=docker provocon/coremedia-build version
Client:
 Version:           26.0.2
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        3c863ff
 Built:             Thu Apr 18 16:26:34 2024
 OS/Arch:           linux/amd64
 Context:           default

$ docker run --name buildx --rm -it --entrypoint=docker provocon/coremedia-build buildx version
github.com/docker/buildx v0.14.0 171fcbeb69d67c90ba7f44f41a9e418f6a6ec1da

$ docker run --name mvn --rm -it --entrypoint=mvn provocon/coremedia-build -v
Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
Maven home: /usr/local/maven
Java version: 17.0.11, vendor: Azul Systems, Inc., runtime: /usr/local/zulu17.50.19-ca-jdk17.0.11-linux_musl_x64
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "6.1.0-18-amd64", arch: "amd64", family: "unix"

$ docker run --name node --rm -it --entrypoint=node provocon/coremedia-build -v
v20.12.1

$ docker run --name helm --rm -it --entrypoint=helm provocon/coremedia-build version
version.BuildInfo{Version:"v3.15.2", GitCommit:"1a500d5625419a524fdae4b33de351cc4f58ec35", GitTreeState:"clean", GoVersion:"go1.22.4"}

To call the container image use

docker run -it --rm provocon/coremedia-build /bin/bash