Create cdist release 7.0.1 #356

Open
opened 2022-12-20 16:58:59 +00:00 by nico · 2 comments
Owner

Targets:

  • Fix #353
  • Cleanup the build process
  • Create a container image for the web content to be able to deploy in k8s
Targets: * Fix #353 * Cleanup the build process * Create a container image for the web content to be able to deploy in k8s
Collaborator

I'd like to release 7.1.0 once the following Pull Requests are merged:

  • #365 cdist 'polyglot' support
  • #373 dnf support (package manager for Fedora/RHEL/CentOS/Rocky/Alma...)
  • #374 support for Rocky and Alma Linux
I'd like to release 7.1.0 once the following Pull Requests are merged: * #365 cdist 'polyglot' support * #373 dnf support (package manager for Fedora/RHEL/CentOS/Rocky/Alma...) * #374 support for Rocky and Alma Linux
Author
Owner

Some notes regarding the website / contrib, also for information to @kjg:

  • the website should be put into a docker container, including all previous releases

The release process should be, imho, version (a) static

  1. build container with all relevant files
  2. bump the argocd container image version -- we need to see how to nicely automate this

I'm also open for a build that is more generic and more dynamic build (b), such as:

  • we have one docker image for all version, without data (nice!)
  • on startup we clone the git repo of cdist
  • for each tagged version we build the documentation
  • once done, we start an nginx
  • potentially run a git pull && rebuild in the background

Either way, we should have a process that creates a website containing all old releases as well as the current release.
The build time required is a secondary concern, even if the build would take an hour, this is not a problem, as the previous container (in the dynamic version) still runs.

The advantage of the static version is no external dependency, aside from the image hosting, but has bigger / more images.

Some notes regarding the website / contrib, also for information to @kjg: - the website should be put into a docker container, including all previous releases The release process should be, imho, version (a) static 1) build container with all relevant files 2) bump the argocd container image version -- we need to see how to nicely automate this I'm also open for a build that is more generic and more dynamic build (b), such as: - we have one docker image for all version, without data (nice!) - on startup we clone the git repo of cdist - for each tagged version we build the documentation - once done, we start an nginx - potentially run a git pull && rebuild in the background Either way, we should have a process that creates a website containing all old releases as well as the current release. The build time required is a secondary concern, even if the build would take an hour, this is not a problem, as the previous container (in the dynamic version) still runs. The advantage of the static version is no external dependency, aside from the image hosting, but has bigger / more images.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ungleich-public/cdist#356
No description provided.