work out the fedup URL for the build and pass it to openQA
AbandonedPublic

Authored by adamwill on Jul 22 2015, 9:05 PM.

Details

Summary

fedup URLs are a bit tricky to work out. fedfind does the hard
work, though; fedfind releases have a property called https_url
_generic which is the URL for the top of the 'generic' tree.
The fedup URL can be easily derived from there. In this approach
we work out the fedup URL here and pass it into openQA as a
variable. The fedup test can then just read the variable out.

Test Plan

Check that the FEDUPURL variable is set correctly when running
the fedup tests. There will be a corresponding diff for
openqa_fedora to use it.

Diff Detail

Repository
rOPENQA fedora_openqa
Branch
fedup
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 36
Build 36: arc lint + arc unit
adamwill retitled this revision from to work out the fedup URL for the build and pass it to openQA.Jul 22 2015, 9:05 PM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.

This plus D471 should address T478.

garretraziel was working on a different approach to this which involved using the fedfind command line in the guest to get the fedup URL, but I always kinda preferred the idea of doing it this way, and it turns out to be pretty clean. We already have the fedfind instance in trigger, we just have to shuttle the necessary property around a bit.

I was hoping that we could use solution that doesn't require user to pass any additional variables besides BUILD - we are executing tests from command line by hand from time to time (mainly during development). Jozef, what do you think?

jskladan requested changes to this revision.Jul 23 2015, 8:36 AM

Although the patches look like a working solution, I'd much prefer the solution discussed in T478.

This revision now requires changes to proceed.Jul 23 2015, 8:36 AM
adamwill abandoned this revision.Aug 13 2015, 3:08 PM

I'm abandoning this as fedup is dead, we'll come back to this when the new upgrade solution is testable I guess.