Foreman Blog

Packit-based nightlies or how to properly test plugins in production

The Foreman Project offers “nightly” repositories (rpm, deb) for everyone who wants to try out the latest changes in a production-like1 setup. This is great to verify changes before they hit the next Foreman release.

However, these repositories have one problem: only a few packages are truly built every day (or night), the majority still requires people to prepare a release of the code. This is done quite intentionally, as it keeps the repositories in a state where preparing a full Foreman release is rather quick, as only few packages need immediate human attention. The downside is that you don’t get the absolute latest changes to try out.

For a while now, we had Packit available for GitHub Pull Requests, which meant you could get an RPM with the changes from a PR and install that on a regular nightly setup. Those builds are only kept for 60 days and easily get out-of-date once the PR is merged, which means they are great to test that explicit change, but not suitable for full integration testing of all components.

Enter the @theforeman/develop COPR! This is a new COPR repository we offer, built by Packit, that contains builds of every single commit made to the main branches of our git repositories.

There is no testing or verification of the contents in this COPR. If the RPM could be built, it will be published, even if the code is broken or dependencies can’t be satisfied.

If you’re still eager to try this out after all these warnings:

This will use the “nightly” repository on https://yum.theforeman.org for Rails, Puma, etc. and the @theforeman/develop COPR for Foreman and plugins.

You can also enable the COPR on an existing system and either use dnf upgrade to update all available packages, or selectively install certain packages you want to try out, like you would upgrade a normal nightly deployment.

  1. Nobody would really run nightlies in prod, right?! 

foremanctl 1.0 - deploying Foreman in Containers reaches first milestone

Over the past few months, we’ve been working on a new way to deploy and manage Foreman and its components (like Katello, Candlepin, and Pulp) using containers. Today, we’re happy to share that foremanctl 1.0 has been tagged, marking our first milestone toward a fully containerized Foreman experience.

betadots consulting services

betadots GmbH joins the group of companies that provide professional services for Foreman!

Sunsetting rsync.theforeman.org

We’re plannig to shutdown rsync.theforeman.org on 2024-06-03, if you’re using it to mirror our repositories, please switch to HTTP(S) based mirroring.

Provisioning Ubuntu Autoinstall

Foreman supports provisioning hosts running Debian and Ubuntu on VMware, Proxmox, cloud providers such as Microsoft Azure, and bare metal hosts. With the Katello plug-in, provisioned and registered hosts receive versioned DEB content based on their lifecycle. This blog article is a short summary of what happened behind the scenes to provisioning hosts running Ubuntu 20.04.3+, why you need new templates, and how to use the new deployment mechanism.

Foreman 3.16.1 has been released! Follow the quick start to install it.

Foreman 3.15.1 has been released! Follow the quick start to install it.