-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PLATFORMCI-179 - Gather the requirements related to the integration of Jenkins and rpmdiff #21
Comments
Ondrej Vasik says: |
Petr Muller added a comment - 29/May/15 2:37 PM |
PLATFORMCI-179 |
Jakub and Miroslav are working on RPMDiff integration to CI, asking them for needinfo now. |
Will this be done using rhpkg? Or calling the rpmdiff command directly now On Wed, Sep 7, 2016 at 8:36 AM, ohudlick [email protected] wrote:
|
Hi, My name is Miroslav Vadkerti, and I am currently taking over the RPMdiff in CI after Peter. Let me try to summarize the current state of RPMdiff in CI and (a bit) where we are heading. Jakub has implemented a proof-of-concept (POC) and it is now enabled for scratch builds of the setup component [1] in BaseOS CI. For testing itself, the production RPMdiff instance is used (meaning the same machines do the testing that for the Errata Tool, but the results are stored in a separate database). The results are viewable in the Adhoc RPMdiff Web UI [2]. The POC works quite nicely, see results for setup scratch builds [3]. The scheduling is currently done in two ways [4]:
Note that the scheduling logic will most likely change once RPMdiff gets a proper REST API [5]. Currently rhpkg uses a temporary limited json-rpc [6]. RPMdiff is not yet decoupled from Errata, there is just a "new" nice and maintained Adhoc Web UI [2] that will replace Errata Web UI in the future. Decoupling is planned to be done in 2017 entirely and will require quite a lot of effort. Anyway the decoupling does not block RPMdiff in CI in any way ... Let me share my a brief overview of my next steps here:
I will be on PTO next two week, so expect a two-week delay for progress of the above. Anyway let me know if you would have any additional questions, I will be glad to answer them :) [1] http://baseos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/setup/view/All%20releases/view/4%3A%20Detailed/ |
"Need to figure out how Jenkins can be used to trigger jobs in rpmdiff.
(I don't think this needs to be resolved during the pilot)"
The text was updated successfully, but these errors were encountered: