<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/roles/kolla-build-config/templates, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=master</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2026-09-28T09:16:14+00:00</updated>
<entry>
<title>CI: Remove is_upgrade guard for kolla-build.conf.j2</title>
<updated>2026-09-28T09:16:14+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-09-28T09:13:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=abc6e01cc0575f24d5091c35f32fc5f0d512cc65'/>
<id>urn:sha1:abc6e01cc0575f24d5091c35f32fc5f0d512cc65</id>
<content type='text'>
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/1007677

Change-Id: Ie4e1a9aa80b03c589e9e94f27c4a6be54e8b146d
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>CI: Don't build from Zuul overrides in upgrade jobs</title>
<updated>2026-08-24T18:20:41+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-08-24T13:10:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=866f53ee7aaf8319a15c5d44625daaee3092808c'/>
<id>urn:sha1:866f53ee7aaf8319a15c5d44625daaee3092808c</id>
<content type='text'>
Our upgrade jobs don't have their own set of required-projects, so we
end up using master version of Zuul cached repos and previous-release
u-c - which obviously breaks.

Change-Id: Ib381c5226b0407deea11ae70188ab2f2239d08eb
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
Signed-off-by: Bartosz Bezak &lt;bartosz@stackhpc.com&gt;
</content>
</entry>
<entry>
<title>CI: Switch to build from Zuul cached repos</title>
<updated>2026-08-18T05:18:38+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2026-08-17T06:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=3f01507eb215b2162e9815257cbd2ba4091251df'/>
<id>urn:sha1:3f01507eb215b2162e9815257cbd2ba4091251df</id>
<content type='text'>
Instead of overloading tarballs.opendev.org (and relying on their
functional state), let's build images directly from Zuul cached
workspaces.

Adding a script that will validate if we're missing anything when
adding new images.

Change-Id: Ie1d8dce841b9a996e96e3a6e1b097b0d256c0bea
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>[CI] Support building source images with in-review changes</title>
<updated>2020-09-16T07:39:41+00:00</updated>
<author>
<name>Mark Goddard</name>
<email>mark@stackhpc.com</email>
</author>
<published>2018-10-02T11:12:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=6bfe9b8749c9a41b3d37816879bb0fac1fdd60d5'/>
<id>urn:sha1:6bfe9b8749c9a41b3d37816879bb0fac1fdd60d5</id>
<content type='text'>
Following this change it is possible to add 'Depends-On' lines to a
kolla commit message that point to reviews in other projects. For
example, this could be used to test building and deploying container
images containing a change to the nova project that is currently in
review.

It also allows to introduce jobs testing against Kolla in other
projects.

The kolla-build-config Ansible role can also be used by other projects,
such as kolla-ansible, to generate the necessary configuration.

This takes us closer to the Kolla Builder - Next Generation concept [1].

[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014255.html

Change-Id: Ia2efa6b5d7278b75ab8dec23207f92d6bd7c58f0
Co-Authored-By: Radosław Piliszek &lt;radoslaw.piliszek@gmail.com&gt;
</content>
</entry>
</feed>
