4.2. Building From the Console
When to Use It
- When you want to turn source code into a container image without writing a Dockerfile
- When you want to run a build from a screen and deploy the result right away
- When the application is simple and does not need a Jenkins pipeline
If you need repeated runs or a deployment approval process, use Jenkins (see 4.4).
The Relationship Between a Build Config and a Build
Two things need to be distinguished.
| Name | What it is | In concrete terms |
|---|---|---|
| Build config (BuildConfig) | A reusable template holding "what to build and how" | A configuration resource stored in the cluster |
| Build | One execution of that config | A Job running in the cluster |
Once you create a build config, you only have to select Start build whenever the source changes. Each run creates a new build and accumulates as history.
The build config by itself does nothing. It is only stored, and the work is created from its contents when you run it.
The Build Config List
Go to Build > Build Configs.

| Column | Description |
|---|---|
| Name | The build config name |
| Namespace | The namespace the build config belongs to |
| Git URI | The repository the source comes from |
| Builder Image | The image responsible for compilation |
| Output Image | The name of the image to be created |
| Age | Time elapsed since creation |
If the list is empty, a guidance message appears with a Create build config button. This is the first screen you see, so start there.
On clusters where the build feature is not installed, a guidance banner appears instead of the list. Ask operations staff to install the build feature.