Skip to content
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

Open
gsr-shanks opened this issue Jul 18, 2016 · 6 comments

Comments

@gsr-shanks
Copy link
Member

"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)"

@gsr-shanks
Copy link
Member Author

Ondrej Vasik says:
"For rpmdiff, we would need to either run them on our instance of rpmdiff
(like rhpkg rpmdiff does atm. - it uses instance from mvadkert)
or we have to wait until rpmdiff is detached from ET. This is on the
long term roadmap, however I don't think there is some ETA atm."

@gsr-shanks
Copy link
Member Author

Petr Muller added a comment - 29/May/15 2:37 PM
"First step is to make it running: and we can easily use rhpkg there, at
least for scratch builds: rhpkg rpmdiff consumes task ids, we get them
via CI infrastructure already, and we can just call rhpkg rpmdiff,
which even guesses some good enough baseline."

@gsr-shanks
Copy link
Member Author

PLATFORMCI-179

@gsr-shanks gsr-shanks changed the title Gather the requirements related to the integration of Jenkins and rpmdiff PLATFORMCI-179 - Gather the requirements related to the integration of Jenkins and rpmdiff Jul 18, 2016
@gsr-shanks gsr-shanks reopened this Jul 18, 2016
@ohudlick
Copy link

ohudlick commented Sep 7, 2016

Jakub and Miroslav are working on RPMDiff integration to CI, asking them for needinfo now.

@jethbu
Copy link

jethbu commented Sep 7, 2016

Will this be done using rhpkg? Or calling the rpmdiff command directly now
that it is decoupled from errata?

On Wed, Sep 7, 2016 at 8:36 AM, ohudlick [email protected] wrote:

Jakub and Miroslav are working on RPMDiff integration to CI, asking them
for needinfo now.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARK96Za4GCmwFvZWUMK06EFvS7QKWiY9ks5qnq_NgaJpZM4JOpGX
.

@thrix
Copy link
Contributor

thrix commented Sep 9, 2016

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]:

  • for scratch builds: "rhpkg rpmdiff ..." is used, as rhpkg does not support non-scratch builds
  • for non-scratch builds directly "rpmdiff-cli" tool is used (AFAIK there are no runs currently using this scenario).

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:

  1. prepare use cases for RPMdiff testing in CI (gathered from Developers and QE)
  2. present the use cases for the PnT Tech Steering Team, RPMdiff development and in this ticket
  3. generalize rpmdiff-baseline (more about this microservice in the presentation above)
  4. meet with Jakub to discuss implementation of required features from CI side
  5. meet with RPMdiff developers to discuss implementation of required features from CI side
  6. Implementing/Testing ...

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/
[2] https://rpmdiff.engineering.redhat.com/
[3] https://rpmdiff.engineering.redhat.com/run/?type=comparison&score=&name=setup&version=
[4] https://code.engineering.redhat.com/gerrit/gitweb?p=baseos-ci.git;a=blob;f=scripts/baseos_ci/rpmdiff.py;h=fc4f4590a26d5e35b6c3212a77a60bbc451d656c;hb=HEAD#l41
[5] ~October 2016 according to the current roadmap:
https://docs.engineering.redhat.com/display/HTD/RPMDiff+Roadmap
[6] https://rpmdiff.engineering.redhat.com/json/browse/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants