Packages from 'feature/nfv' branch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Alexander Evseev | ||
9.x |
Fix Released
|
High
|
Alexander Evseev |
Bug Description
There is a bug for building new packages for NFV feature [0].
Those packages are not going to be released as part of 9.0, but must be available for those who wants to use it with 9.0.
To achieve this a kind of 'feature' package repository is required.
There is a 'feature/nvf' branch in git repositories of every package we need [1].
What is missed is a support on CI side. Ideally it would be great to get the following workflow:
1. On commit to 'feature' branch package build process triggers
1.1 Package published to a temporary CR related repository.
1.2 After a package was built install tests run (how to map with target repo for install test?)
1.3 After install tests run systest runs (how to map with target ISO for systest?)
2. After a package was built (+tests passed) it is published to 'feature' package repository
Right now we need only points 1 and 1.1 from the list above.
However, to fully support feature branches / repositories the entire workflow should be implemented (and probably improved.
[0] https:/
[1] https:/
Changed in mos: | |
assignee: | nobody → Fuel CI (fuel-ci) |
importance: | Undecided → High |
milestone: | none → 9.0 |
Changed in mos: | |
status: | New → Confirmed |
tags: | added: area-ci |
tags: | removed: need-info |
Changed in mos: | |
assignee: | Fuel CI (fuel-ci) → Alexander Evseev (aevseev-h) |
no longer affects: | mos/10.0.x |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
actual result
expected result
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug