Automate Container Image Build and Push

[janhalen]

Description

Establish an automated process to build the openclient-core operating system image. This ensures that every update to the repository results in a new, versioned image stored in the GitHub Container Registry, ready for deployment.

• Define the Build Workflow

  • Create a build YAML file

• Configure the Build Environment

  • Define the automation to trigger (e.g. on "push" events to the main branch.)
  • Use a build runner (e.g. like quay.io/buildah/stable) to host the build process.

• Establish Registry Authentication

  • Use the built-in GITHUB_TOKEN to allow the automation to securely log into the GitHub Container Registry.

• Build the Image

  • Use the standard tooling in the selected portable environment build the image using the selected portable build environment.

• Apply Version Tags

  • Configure the automation to tag the image with a semantic version and a secondary tag using the unique "Commit SHA" for precise version tracking.

• Push and Verify

  • Manually verify the image is visible in the container image repo.

Definition of Done

• The image build is performed inside a portable build environment container, (not via a GitHub-managed plugin.)
• The resulting image is successfully pushed to the registry.
• The build script has been tested locally to ensure portability.
• The system is ready to be migrated to a self-hosted forge if required.

[janhalen]

@ChatBotBerg & @turegjorup : Can you make the needed agreements to put this "in the books"

@turegjorup please comment, critique and suggest changes to this high level issue description and give an estimate when we agree on a set of minimal tasks to meet the DoD.