congress does not respect devstack branch
Bug #1503353 reported by
Tim Hinrichs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
congress |
Fix Released
|
Low
|
Madhu Mohan Nelemane |
Bug Description
To run all the openstack projects for a given branch B such as stable/liberty, you simply do a git-checkout -b B within devstack before running stack.sh. This causes devstack to run git clone ... -b B for every project it installs.
When following the devstack install instructions for Congress but cloning devstack with -b B, the B branch is not checked out for Congress; instead master is checked out.
I suspect devstack provides the B branch as an environmental variable (or something similar), and the congress contrib/devstack scripts do not properly deal with that variable.
Changed in congress: | |
importance: | Medium → Low |
Changed in congress: | |
assignee: | nobody → shravya Gaddam (shravya-g90) |
Changed in congress: | |
assignee: | shravya Gaddam (shravya-g90) → nobody |
Changed in congress: | |
assignee: | nobody → Madhu Mohan Nelemane (mmohan-9) |
To post a comment you must log in.
It seems we are using the CONGRESS_BRANCH as we should be doing. But it seems it doesn't get properly set.
I'm told on #openstack-infra that the gate will do the proper thing, so mainly this is a problem for end users trying to check out the stable/liberty branch via devstack.