Starting September 15th you’ll be able to use OSBS 2.0 for your container builds. We’ll send a second announcement once OSBS 2.0 will be GA.

At first, since we won’t set OSBS 2.0 as the default build service, you’ll need to explicitly use it (hence the opt-in). The more teams will use it, the better, as we’ll be able to catch more bugs/issues that our testing might have missed. 

Why should you opt-in to using OSBS 2.0?

In addition to benefiting from performance and reliability improvements, by helping us test OSBS 2.0 now, you’ll have a headstart when we make it the default build system for all teams in October. We have an aggressive timeline (November 15th due date) for disabling OSBS 1, so the more testing we can do now, the better.

How to use OSBS 2.0 for your team?

You have to use a brew command with the channel-override option:

• brew container-build TARGET git://pkgs.devel.redhat.com/containers/REPO#COMMIT –git-branch=BRANCH --channel-override=container-binary

• For CPaaS specify brew flags [1] in your brew build config

• brew-flags: --channel-override=container-binary

Unfortunately, rhpkg tool doesn’t support channel overrides so for the opt-in phase, only brew CLI can be used for OSBS 2.0

What changes from OSBS 1 can you expect?

• OSBS 2.0 no longer contains the auto-rebuild feature, so if you’re still using that, it will stop working.

• OSBS 2.0 will no longer store images in the brew archive.

• Only podman is used as the image build engine (no docker or imagebuilder).

• Otherwise, you should see feature parity with OSBS 1.

So why did we do this entire effort?

OSBS 1 is running on old hardware (and old OCP 3.11 - for which the official support from IT already ended) and we decided to also refactor OSBS to make it future-proof, whilst also moving it to newer hardware. This change also makes OSBS 2.0 more compatible to be integrated into HACBS in the future. We also expect performance improvements and reliability improvements behind the scenes but we’ll know more about it after using OSBS 2.0 for some time.

With best regards your SP CLOUD Build team.

[1] https://cpaas.pages.redhat.com/documentation/schema/product/builds/brew_container.html#_build_section_keys