#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: production | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by tflink):
Replying to [comment:4 kparal]:
I don't like character swapping much, because the filename tries
to
reflect the ID that was defined by the test itself. I would prefer not to
change the ID. It will be used in more places than just Bodhi (currently
just in opt-in emails, true).
I see your point about renaming the logs, it would be better to just keep
the URL constructed from the package name.
It is not hard to create our own shortening service and run it on
our
autoqa server instance. However, I would rather invest the time elsewhere
and just go with some public shortening service. I don't see anything
wrong with that, our results are short-lived anyway (1 month max before
they are deleted) and AutoQA is in heavy development. My approach is to
take the easiest path here. What do you think?
I think that it's worth spending some effort on this but not too much -
akin to what we were doing for 0.5.0.
I'm not completely against using a public service but I have two concerns
about doing so:
1. Make sure that we don't get blacklisted for submitting urls at too
high of a rate
1. I think it would look a little strange to have bit.ly (or any other
service) urls in the bodhi comments.
Adding a self-hosted URL shortening service (TightURL or lilURL are the
first ones that come to mind) might be a better balance. I set up lilURL
as a demo a couple of months ago and it really didn't take long (maybe 2
hours but I think it was less) - the hardest part was working around the
default Autotest rules in Apache. We could end up with something along the
lines of
*
http://autoqa.fedoraproject.org/tests/<UID>
*
http://autoqa.fedoraproject.org/result/<UID> (results is used by
autotest and I think it would be unwise to start remapping all that)
* Anything else you can think of
Since it would be self-hosted, we can restrict the incoming requests and
don't really have to worry so much about spamming and abuse but would be
able to avoid any objections to using an outside service.
If we take some public shortening service approach, it will be great
(but not strictly necessary) if:
* the service itself is opensource (that is not required for me in
this
case, but I imagine other people could object)
Agreed -
tighturl.com (TightURL) and ur1.ca (lilURL) are two that I'm
aware of if we choose to go that route.
* we could specify some suffix to make the links more readable, so
that
we have somethink like:
http://bit.ly/xH8dJ/maven-3.0.3-7.fc15.html
Interesting idea but I'm not sure any current services support that. Worth
looking into, though
Do you have tips for such services?
I guess that I'd prefer setting something up on our own but I'm not
completely set on that.
Another solution that I just thought of would be to use mod_rewrite to
allow for different urls in bodhi:
* Logs would still be named 'package-1.2-3.fc99.html'
* Comments in bodhi would be 'package_1.2_3.fc99.html'
* mod_rewrite would redirect the bodhi link to 'package-1.2-3.fc99.html'
We would probably want to do something a little more clever than just
replacing '-' with '_' in the bodhi link to make the rewrite rules a
little more sane but the same basic concept would hold.
I'm not 100% sure that this would work well with Autotest's current apache
config but I can think of ways to make it work if we don't want to mess
with the defaults.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/347#comment:5>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project