834d9da342
Now that stx-openstack application is more up-to-date with OpenStack releases timeline, using "stable/<release>" git references is not advised since such branches can receive fixes cherry-picks on upstream repos and therefore make our stx-* images build not fixed to a given source code version [1]. This change sets all upstream repos references to commits SHAs, as per of today 2024 Feb 16th, so StarlingX release 9.0 will have a stable and reproducible build. If there is the need of cherry-picking any OpenStack upstream fix, this should be handled by a specific task/launchpad later (on StarlingX master branch). With the commit SHAs aligned, application release info can be set to StarlingX 9.0 release (as peer other applications). [1] https://bugs.launchpad.net/starlingx/+bug/2052644 Story: 2010715 Task: 49588 TEST PLAN: PASS: build-helm-charts.sh --os debian --package stx-openstack-helm-fluxcd --app stx-openstack PASS: build-wheel-tarball.sh --keep-image PASS: build-stx-images.sh --only stx-aodh,stx-ironic,stx-barbican, stx-ceilometer,stx-cinder,stx-glance,stx-heat,stx-horizon, stx-keystone,stx-neutron,stx-nova,stx-placement Change-Id: Id1cf2cbd49f0b2b5fb7d02524794310d92be8f22 Signed-off-by: Thales Elero Cervi <thaleselero.cervi@windriver.com> |
||
|---|---|---|
| .. | ||
| debian | ||
| Readme.rst | ||
This repo is for https://opendev.org/openstack/horizon
Changes to this repo are needed for StarlingX and those changes are not yet merged. Rather than clone and diverge the repo, the repo is extracted at a particular git SHA, and patches are applied on top.
As those patches are merged, the SHA can be updated and the local patches removed.
It is also used to build the stx-horizon image, based on https://opendev.org/openstack/horizon