Are most grenade plugin projects doing upgrades wrong?
elod.illes at ericsson.com
Thu Jun 13 16:13:33 UTC 2019
Actually, if you check  and , they seemingly check out master, but
just below the linked line like 20 lines, there's a 'git show --oneline'
and 'head -1' which shows that the branch is clearly stable/stein. So it
seems there's no need for explicit branch settings in ... but I
haven't found the code lines which cause this behavior, yet...
On 2019. 06. 13. 15:45, Matt Riedemann wrote:
> While fixing how the watcher grenade plugin is cloning the watcher
> repo for the base (old) side  to hard-code from stable/rocky to
> stable/stien, I noticed that several other projects with grenade
> plugins aren't actually setting a stable branch when cloning the
> plugin for the old side . So I tried removing the stable/stein
> branch from the base plugin clone in watcher  and grenade cloned
> from master for the base (old) side . Taking designate as an
> example, I see the same thing happening for it's grenade run .
> Is there something I'm missing here or are most of the openstack
> projects running grenade via plugin actually just upgrading from
> master to master rather than n-1 to master?
>  https://review.opendev.org/#/c/664610/1/devstack/upgrade/settings
>  https://review.opendev.org/#/c/664610/2/devstack/upgrade/settings
More information about the openstack-discuss