or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Unifying rpm building process in CI
Problem Statement
In TripleO Deployment, in upstream and downstream all the tripleo & infrared CI jobs deploys tripleo using
RPM.
in Tripleo CI, we have build-test-packages role https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/roles/build-test-packages.
It is an Ansible role for generating custom RPMSs from upstream Gerrit changes in the TripleO project using DLRN. This repo then can be injected in the tested environment, a repo file created and a yum update should start using the built RPMs.
For example: A developer working on tripleo-ansible patch and tripleo-heat-templates patch and wanted to test it together then, He pushed the tripleo-ansible patch
and then add Depends-On: <tht patches> in the commit message. During TripleO CI run, build-test-packages extracts the tripleo-ansible commit message and depends-on tht patches
using zuul deps.py. Then it uses rdoinfo to find the right project and then same information is passed to DLRN to build both packages from that commit. Once packages are built.
It creates a yum repo and passed it tripleo jobs where yum update operation updates the latest package.
The same thing is not possible in downstream. It makes downstream developers hard to test the patches in downstream dist-gits.
We have https://pagure.io/zuul-distro-jobs (maintained by PCD team) which contains all building blocks for above scenario. So now we have multiple tools doing same things.
We want to remove the maintaince and work on using one tool to solve the above problem.
Solution
Things to discuss