Document/Link to the RDO spec update process in the docs
Bug #1651104 reported by
Julie Pichon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Expired
|
Undecided
|
Unassigned |
Bug Description
Packages are built on the fly on DLRN to test incoming gerrit patches. When a new dependency is added, it also needs to be included in the spec by updating the appropriate distgit [1][2], or the patch will fail CI. This is confusing to debug and seems to only be transmitted via tribal knowledge so far. It would be good to document both the process and which CI logs to consult to get at the package building info. This could perhaps be added as a section under the developer docs at [3]?
[1] https:/
[2] https:/
[3] http://
Changed in tripleo: | |
milestone: | none → ocata-3 |
Changed in tripleo: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in tripleo: | |
milestone: | ocata-rc1 → pike-1 |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
To post a comment you must log in.
This should go into the ui-specific documentation that we're planning to write. But I agree that for now, we should add it to the developer docs as per above.