[AutoQA] #347: Test results are sometimes linked incorrectly in Bodhi

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |       Owner:            
     Type:  defect      |      Status:  new       
 Priority:  major       |   Milestone:  Hot issues
Component:  production  |    Keywords:            
------------------------+---------------------------------------------------
 Some Bodhi comments links are split in half, breaking the hyperlink:

  * https://admin.fedoraproject.org/updates/gnome-commander-1.2.8.12-1.fc15
  * https://admin.fedoraproject.org/updates/tzdata-2011h-1.fc15

 But some links are OK, even though the text length is about the same (and
 it's even from the same test run):

  * https://admin.fedoraproject.org/updates/xmlcopyeditor-1.2.0.4-1.fc14

 Is it our problem or Bodhi problem?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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):

 This appears to be inside bodhi. When processing the comments, bodhi uses
 textwrap.!TextWrapper(width=80, break_long_words=False)

[http://git.fedorahosted.org/git/?p=bodhi.git;a=blob;f=bodhi/controllers.p...
 see bodhi source]

 For python < 2.6, this will always break on hyphenated words (gnome-
 commander, tzdata-201h) but will not break on non-hyphenated words
 (xmlcopyeditor). For python >= 2.6, the argument break_on_hyphens is
 available that keeps hyphenated words from being broken.

 To test this, use the following code:
 {{{
 #!python

 import textwrap
 u =

'http://autoqa.fedoraproject.org/results/136419-autotest/172.16.0.19/depcheck/results
 /gnome-commander-1.2..html'
 textwrap.TextWrapper(width=80,break_long_words=False).fill(u)
 }}}

 The result is:
 {{{

'http://autoqa.fedoraproject.org/results/136419-autotest/172.16.0.19/depcheck/results\n
 /gnome-commander-1.2..html'
 }}}

 If the break_on_hyphens=False option is used in newer python:
 {{{
 #!python

 textwrap.TextWrapper(width=80,break_long_words=False,break_on_hyphens=False).fill(u)
 }}}

 The result is:
 {{{

'http://autoqa.fedoraproject.org/results/136419-autotest/172.16.0.19/depcheck/results
 /gnome-commander-1.2..html'
 }}}

 If bodhi is running under python >= 2.6, it would be easy to submit a
 patch to add the break_on_hyphens=False option. If not, we could propose a
 patch for bodhi but it wouldn't be as clean.

 The options I can see for fixing this on our end are:
  1. Replace hyphens in log names with another character ('_' maybe)
  1. Use a URL shortening scheme

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:1>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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:              |  
------------------------+---------------------------------------------------
Changes (by kparal):

 * cc: lmacken (added)

Comment:

 Luke, could you please comment on whether it is possible to fix this
 behavior on the side of Bodhi?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:2>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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):

 I spoke with lmacken about this earlier this week and confirmed that the
 application server hosting bodhi is still running python 2.4 at the
 moment. An upgrade to 2.6 (EL6) is scheduled for some point in the
 mysterious future but AFAIK, no hard upgrade date has been set.

 This means that the simple fix of adding the 'break_on_hyphens=False'
 option isn't going to be available in the near future.

 While it could theoretically be possible to fix this in bodhi by messing
 with the comment parsing logic in the controller, he wasn't convinced that
 would be a good idea. Honestly, I'm not sure its a good idea, either since
 that could possibly break other things and it would be a fix only for us.

 What we seem to be left with is fixing it on our end. In my mind, our best
 options are:
  1. replace '-' with '_' in logfile names
  1. use some url shortening scheme (replace the whole link with a shorter
 ID)

 Changing the log file naming scheme would be the easiest but I'm wondering
 if switching to a URL shortening scheme would make the bodhi comments
 easier to read (assuming we keep using them for the foreseeable future).

 However, if we aren't going to be using bodhi comments for much longer, I
 don't see the utility in doing anything more than switching '-' with
'_'
 in the log names.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:3>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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:              |  
------------------------+---------------------------------------------------
Changes (by kparal):

 * cc: lmacken (removed)

Comment:

 Thanks, Tim, for communicating this.

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

 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?

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

 Do you have tips for such services?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:4>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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

[fedora-badges]

#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 kparal):

 Replying to [comment:5 tflink]:
>   * http://autoqa.fedoraproject.org/tests/<UID>
>  
 This looks great. Or maybe http://autoqa.fedoraproject.org/report/<UID>;.
 Very nice.

 If there are opensource shortening service ready to be deployed (and
 preferably packaged in Fedora) with minimal effort (I didn't know that),
 it sounds like a reasonable approach.

>  Agreed - tighturl.com (TightURL) and ur1.ca (lilURL) are two that
> I'm
>  
 aware of if we choose to go that route.

 Thanks for the links. Good to they something like this exists.

>  I guess that I'd prefer setting something up on our own but
> I'm not
>  
 completely set on that.

 Me neither, but you convinced me that deploying our own service doesn't
 have to as time-consuming, and there are some benefits. I think I am fine
 with both approaches (our service or external service).

>  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'

 I am afraid a little about all those re-writes. It adds some complexity
 and may make debugging harder.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:6>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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:6 kparal]:
>  If there are opensource shortening service ready to be deployed (and
>  
 preferably packaged in Fedora) with minimal effort (I didn't know that),
 it sounds like a reasonable approach.

 Hmm, none packaged in Fedora that I know of. I was originally thinking of
 just installing the shortener since lilURL is a couple of php files and a
 MySQL database but packaging is probably the better route here. Do you
 think that we'd be using it long enough to justify the effort needed to
 package a shortener?

>  > 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'
>  I am afraid a little about all those re-writes. It adds some complexity
>  
 and may make debugging harder.

 Yeah, rewrite rules can be lots of fun but it would be an alternative to
 the URL shortener.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:7>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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 jlaska):

 Replying to [comment:7 tflink]:
>  Yeah, rewrite rules can be lots of fun but it would be an alternative
> to
>  
 the URL shortener.

 mod_rewrite seems perfectly reasonable if it addresses the issues.
 Bugzilla uses this now to redirect http://bugzilla.redhat.com/<bug#> ->
 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<bug#>

 I almost wish autotest didn't include the test client host in the URL.
 Otherwise I think it would be straight forward to redirect by shortening


http://autoqa.fedoraproject.org/results/140952-autotest/172.16.0.20/depch...

  to

 http://autoqa.fedoraproject.org/results/140952/<extra>

 I could probably add multiple rules (one for each test client), but that
 could be a pain.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:8>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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 jlaska):

 Replying to [comment:8 jlaska]:

 Scratch that ... I forgot the URL's contain *both* the test client name
 *and* the test name.  You can ignore my entire previous comment :)

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:9>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#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:9 jlaska]:
>  Replying to [comment:8 jlaska]:
>
>  Scratch that ... I forgot the URL's contain *both* the test client name
>  
 *and* the test name.  You can ignore my entire previous comment :)

 All the more reason to use a URL shortener, I guess. I'm starting to see
 more attraction to Kamil's idea of using the shortener as a base url.

 As a side note, if we do end up packaging (or plan to package) a URL
 shortener, my vote would be for TightURL. IIRC, its a little harder to set
 up but seems to have a more active upstream and better abuse protection.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:10>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:       
     Type:  defect      |       Status:  new  
 Priority:  major       |    Milestone:  0.6.0
Component:  production  |   Resolution:       
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by tflink):

  * milestone:  Hot issues => 0.6.0

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:11>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:       
     Type:  defect      |       Status:  new  
 Priority:  major       |    Milestone:  0.6.0
Component:  production  |   Resolution:       
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 Replying to [comment:7 tflink]:
>  Hmm, none packaged in Fedora that I know of. I was originally
> thinking
>  
 of just installing the shortener since lilURL is a couple of php files and
 a MySQL database but packaging is probably the better route here. Do you
 think that we'd be using it long enough to justify the effort needed to
 package a shortener?
>  
 If nothing is packaged yet, I would definitely install it first and
 package it later, if we decide to be using it in the long term. And by the
 way we will have a new packager in our team (mkrizek), simple url
 shortener can be a good way for him to practise his skills :-)

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:12>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by tflink):

  * owner:  => tflink
  * status:  new => assigned

Comment:

 As discussed in the 0.6.0 planning meeting, we are going to go ahead with
 the URL shortener concept.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:13>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Was decision made on what service we will use? I looked into proposed
 TightURL a little bit and found out that according to
 http://tighturl.com/project/p/tighturl/source/tree/master/ the project
 hasn't been "touched" for a one year and half. Am I missing something?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:14>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 True, there have been no modifications on master for a year and a half but
 since the code isn't that complicated, I would assume that changes would
 stabilize after a while.

 Assuming that one believes everything that is written, the main author is
 working on a new release http://tighturl.com/project/devblog/

 Other suggestions would be welcomed. These were just the only projects
 that I was aware of.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:15>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by jlaska):

 Out of curiousity, anyone know of any non-php (or python) projects?  I
 imaging anything that relies on goo.gl would be frowned on :)
 (http://segfault.in/2010/10/shorten-urls-using-google-and-python/).  Or
 maybe the same applies to bit.ly (http://segfault.in/2010/10/shorten-urls-
 using-python-and-bit-ly/).  One python-based one I did find, doesn't
 appear to be actively maintained (http://nileshk.com/2009/06/02/url-
 shortener-web-app-using-django.html).  But like Tim said, I don't imagine
 these services being terribly complex </famous_last_words>

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:16>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Regarding to those relying on goo.gl or bit.ly, I guess those possibly
 could not satisfy one of Tim's conditions: "Make sure that we don't get
 blacklisted for submitting urls at too high of a rate", right? I would too
 prefer a service written in Python but unless somebody knows of any (which
 is also an active project) I would probably go with TightURL which seems
 to be after all active, is configurable and does not seem to be difficult
 to maintain. What do you think?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:17>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Yeah, I would also prefer to use something written in python but I agree
 that an actively maintained project is more important. There are a couple
 forks of the django based URL shortener that James mentioned that have
 been updated more recently.
  * More recently updated but still a year since any changes
   * https://github.com/voidfiles/url-shortener
  * A branch that appears to be a current work in progress
   * https://github.com/hypatia/url-shortener/tree/pr1v

 Another PHP based project that is very active right now and might be a
 better choice is yourls ( http://code.google.com/p/yourls/).

 I'm planning to set up some of these on a local system today to get a
 better handle on the following questions:
  1. How difficult are they to set up
  1. How well designed is the API - will it fit our needs?
  1. How hard would it be to package?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:18>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by athmane):

 Another option is drupal shorturl(1) module which can be integrated to
 Fedora Insight(2) (Drupal 6 based)

 (1) http://drupal.org/project/shorturl

 (2) http://insight.fedoraproject.org/

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:19>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.6.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 I have initial code for a python client to YOURLS up on github:
  * https://github.com/tflink/python-yourls

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:20>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink           
     Type:  defect      |       Status:  assigned         
 Priority:  major       |    Milestone:  Nice to have soon
Component:  production  |   Resolution:                   
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by kparal):

  * milestone:  0.6.0 => Nice to have soon

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:21>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by kparal):

  * milestone:  Nice to have soon => 0.7.0

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:22>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by lmacken):

 * cc: lmacken (added)

Comment:

 I just updated bodhi to pass 'break_on_hyphens=False' to the TextWrapper,
 if it's available (python 2.6+). Since we're going to be upgrading all of
 our app servers to RHEL6 in the near future, this issue will be resolved
 then.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:23>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 Thanks Luke, that is great. Our URL shortener is on its way already, but
 that change may help in more areas in the future.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:24>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Patch: https://fedorahosted.org/reviewboard/r/215/

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:25>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Replying to [comment:25 mkrizek]:
>  Patch: https://fedorahosted.org/reviewboard/r/215/
>  
 Reviewed.

 At one point, we were talking about trying to make the shortened url look
 kind of like the html we were shortening. Are we still interested in doing
 that?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:26>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 I added comments and replies.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:27>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 I added comments to comments. :)

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:28>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 I added some more comments to the review but I have a couple of questions:

 Are we going to just use {UID} or are we going to go with more detailed
 information in the shortened url (report/package-123-fc16)?

 Are we going to use the shortened URL for emails?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:29>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Replying to [comment:29 tflink]:
>  I added some more comments to the review but I have a couple of
>  
 questions:
>  
 Thanks, I replied.

>  Are we going to just use {UID} or are we going to go with more
> detailed
>  
 information in the shortened url (report/package-123-fc16)?
 For me, I would use just {UID} as this would generate really short urls.
 But I can see us going either way as report/package-123-fc16 is more fancy
 and gives user info about the package (however I don't think it's that
 important in our case).

>  Are we going to use the shortened URL for emails?
>  
 I think it's a good idea, I would go for it.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:30>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Tim and myself were discussing what the url would look like and we came up
 with the following:

 archtestabbr-packagename-version

 so a real example would be:

 http://autoqa.fedoraproject.org/report/x86dc-yourls-1.5-4.fc15

 "dc" of course stands for depcheck, then we would have "up" for
 upgradepath. Package names that are longer than 20 would be truncated. In
 case of duplicity we would add a number to testabbr so:
 x86dc2-yourls-1.5-4.fc15 and we would add up to let's say number 4? So we
 don't retrying 100 times. So instead of adding number 5, we would use
 whatever url yourls provides us.

 Note: Putting arch and test name into url will increase a chance that we
 won't end up with whatever url yourls provides us too soon in case of
 duplicity of url (= more meaningful urls).

 DontForget: to change the yourls config to accept "-" and "."

 Any comments/objections?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:31>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 AFAICT we don't need the links to be super-short, just "short enough".
 That means I would like to include some reasonable identifier of the
 report instead of just UID.

 Regarding the proposal in comment 31:
  1. Let's put there architecture in the link. "x86" for 32bit,
"x64" for
 64bit, and nothing for noarch?
  2. Test names abbreviations are also a good idea. But how do you intend
 to create such names? If you don't want to manually provide these
 shortcuts inside every test (I am opposed), how will you generate
 reasonable shortcuts (like "dc" or "up")? I don't think it's
doable. What
 about this - let's use first 4 characters of the test - "upgr",
"depc",
 "rpml", "rpmg", "rats" (for rats_install and rats_sanity),
"anac" (for
 anaconda_storage and anaconda_checkbot), etc.
  3. Let's truncate test ID at 20 characters (please note that test ID
 doesn't have to be a package name!), yes.
  4. In case of duplicity, let's add an increasing number, yes.
  5. No, don't fall back to simple UID after several duplicate hits.
 Increasing the sequence number to 100 or 1000 is still better than using
 pure UID. The first approach still tells me test name, architecture and
 test ID, UID tells me nothing. Imagine how fast the duplicate count would
 be depleted according to your proposal for "gnome-shell-extension-
 alternative-status-menu" package. Just after few updates.
  6. Let's restructure the URL a bit. What about?
  * http://autoqa.fedoraproject.org/report/x86/depc/yourls-1.5-4.fc15
  * http://autoqa.fedoraproject.org/report/x64/depc/2/yourls-1.5-4.fc15
  * http://autoqa.fedoraproject.org/report/upgr/5/gnome-shell-extensio
  * http://autoqa.fedoraproject.org/report/rpml/127/gnome-shell-extensio

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:32>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Replying to [comment:32 kparal]:
>   1. Let's put there architecture in the link. "x86" for
> 32bit, "x64" for
>  
 64bit, and nothing for noarch?

 either nothing or NOA would work but yeah, putting the arch in the url
 sounds like a good idea since it would help differentiate between the
 different results.

>   2. Test names abbreviations are also a good idea. But how do you
> intend
>  
 to create such names? If you don't want to manually provide these
 shortcuts inside every test (I am opposed), how will you generate
 reasonable shortcuts (like "dc" or "up")? I don't think it's
doable. What
 about this - let's use first 4 characters of the test - "upgr",
"depc",
 "rpml", "rpmg", "rats" (for rats_install and rats_sanity),
"anac" (for
 anaconda_storage and anaconda_checkbot), etc.

 Are we going to be shortening the URLs to all of those test results?

>   5. No, don't fall back to simple UID after several duplicate
> hits.
>  
 Increasing the sequence number to 100 or 1000 is still better than using
 pure UID. The first approach still tells me test name, architecture and
 test ID, UID tells me nothing. Imagine how fast the duplicate count would
 be depleted according to your proposal for "gnome-shell-extension-
 alternative-status-menu" package. Just after few updates.

 I think that the idea was to keep the number high enough that we're not
 likely to use a UID but low enough that shortening the URL isn't going to
 get caught in a long loop. I think that we need to set an upper limit in
 case we do end up in a long loop - letting the shortening method try 200
 urls because we don't want to use a generic UID is silly. I don't think
 that martin or I were really stuck on 4, it just seemed like a good place
 to start.

>   6. Let's restructure the URL a bit. What about?
>   * http://autoqa.fedoraproject.org/report/x86/depc/yourls-1.5-4.fc15
>   * http://autoqa.fedoraproject.org/report/x64/depc/2/yourls-1.5-4.fc15
>   * http://autoqa.fedoraproject.org/report/upgr/5/gnome-shell-extensio
>   * http://autoqa.fedoraproject.org/report/rpml/127/gnome-shell-extensio
>  
 I don't think that slashes are supported by yourls. IIRC, we're limited to
 '-' as a delimiter (if yourls is configured for that) and everything else
 is stripped out ('.', '_' etc.)

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:33>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 Replying to [comment:33 tflink]:
>  >  2. Test names abbreviations are also a good idea. But how do
> you
>  
 intend to create such names? If you don't want to manually provide these
 shortcuts inside every test (I am opposed), how will you generate
 reasonable shortcuts (like "dc" or "up")? I don't think it's
doable. What
 about this - let's use first 4 characters of the test - "upgr",
"depc",
 "rpml", "rpmg", "rats" (for rats_install and rats_sanity),
"anac" (for
 anaconda_storage and anaconda_checkbot), etc.
>  Are we going to be shortening the URLs to all of those test results?
>  
 I believe so. It makes the links more readable, they are shorter, they
 better fit in emails and in web pages. Do we have any concerns why limit
 the shortener just for bodhi-related tests?


>  >  5. No, don't fall back to simple UID after several
> duplicate hits.
>  
 Increasing the sequence number to 100 or 1000 is still better than using
 pure UID. The first approach still tells me test name, architecture and
 test ID, UID tells me nothing. Imagine how fast the duplicate count would
 be depleted according to your proposal for "gnome-shell-extension-
 alternative-status-menu" package. Just after few updates.
>  I think that the idea was to keep the number high enough that we're not
>  
 likely to use a UID but low enough that shortening the URL isn't going to
 get caught in a long loop. I think that we need to set an upper limit in
 case we do end up in a long loop - letting the shortening method try 200
 urls because we don't want to use a generic UID is silly. I don't think
 that martin or I were really stuck on 4, it just seemed like a good place
 to start.

 I understand now, the shortening service is a remote service and for every
 URL proposal you need to ask the server whether it is free, then increment
 the number, then ask again, am I right? That would mean longer and longer
 intervals when finding the next free number.

 OK, another proposal - what about putting *both* UID and test info into
 the URL? We could do something like:
  * http://autoqa.fedoraproject.org/report/UID/arch/test/test_id
 (or with dashes, or with UID at the end)

 That means e.g.:
  * http://autoqa.fedoraproject.org/report/25374-x86-depc-yourls-1.5-4.fc15

 Of course it depends what is possible to ask yourls for.

>  I don't think that slashes are supported by yourls. IIRC,
> we're limited
>  
 to '-' as a delimiter (if yourls is configured for that) and everything
 else is stripped out ('.', '_' etc.)

 OK, we should find that our. Martin, can you please look at it a tell us
 what is supported and what is not? Thanks.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:34>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Replying to [comment:34 kparal]:
>  That means e.g.:
>   * http://autoqa.fedoraproject.org/report/25374-x86-depc-
>  
 yourls-1.5-4.fc15
>  
 I don't think we can use both keyword and UID generated by yourls, Tim is
 that right? We can always generate our own UID like 6 characters so it
 would be a small chance to have a duplicate url, but still there is a
 chance. But other than that, I like this format.

 > Of course it depends what is possible to ask yourls for.
>  
 > > I don't think that slashes are supported by yourls. IIRC,
we're
 limited to '-' as a delimiter (if yourls is configured for that) and
 everything else is stripped out ('.', '_' etc.)
>  
 > OK, we should find that our. Martin, can you please look at it a tell us
 what is supported and what is not? Thanks.

 So we are indeed limited to '-' which is available via plugin. And then
 yourls provides two kinds of encodings:
 Base 36 encoding uses 0123456789abcdefghijklmnopqrstuvwxyz
 Base 62 encoding uses
 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
 The first one is default, so we will need to change that.

 If we wanted to use '/', we'd need to write a plugin (which is rather
 trivial from what I saw) but I don't think we want to have another thing
 to worry about in case of new release inconsistency.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:35>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Updated patch according to the discussion is now in the reviewboard and in
 the ticket347 branch.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:36>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Wow, someone (me) has been a little slow about replying to this.

 Replying to [comment:35 mkrizek]:
>  Replying to [comment:34 kparal]:
>  > That means e.g.:
>  >  * http://autoqa.fedoraproject.org/report/25374-x86-depc-
>  
 yourls-1.5-4.fc15
>  >
>  I don't think we can use both keyword and UID generated by yourls, Tim
>  
 is that right?

 Yes, that is my understanding, too.

>  We can always generate our own UID like 6 characters so it would be
> a
>  
 small chance to have a duplicate url, but still there is a chance. But
 other than that, I like this format.

 We could also base the UID off of the job number in autotest. The last 6
 chars or something?

>  > Of course it depends what is possible to ask yourls for.
>  >
>  > > I don't think that slashes are supported by yourls. IIRC, we're
>  
 limited to '-' as a delimiter (if yourls is configured for that) and
 everything else is stripped out ('.', '_' etc.)
>  >
>  > OK, we should find that our. Martin, can you please look at it a tell
>  
 us what is supported and what is not? Thanks.
>  So we are indeed limited to '-' which is available via plugin. And then
>  
 yourls provides two kinds of encodings:
>  Base 36 encoding uses 0123456789abcdefghijklmnopqrstuvwxyz
>  Base 62 encoding uses
>  
 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
>  The first one is default, so we will need to change that.
>
>  If we wanted to use '/', we'd need to write a plugin (which is rather
>  
 trivial from what I saw) but I don't think we want to have another thing
 to worry about in case of new release inconsistency.

 Yeah, agreed. Let's not make this any more complicated than we have to.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:37>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Replying to [comment:36 mkrizek]:
>  Updated patch according to the discussion is now in the reviewboard
> and
>  
 in the ticket347 branch.

 Reviewed. The only two things I saw were:
  * Starting with 0 on the yourls keyword retries
  * Are we going to start with some UID as discussed here?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:38>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 My replies are in the reviewboard.

 re: UID: Would be the last 6 chars of the job number in autotest unique?
 If not, is combinating both too much? First we can use the UID, if it's
 not unique then we can start adding, instead of UID, numbers in some
 range? I am probably overthinking it...

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:39>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Replying to [comment:39 mkrizek]:
>  re: UID: Would be the last 6 chars of the job number in autotest
> unique?
>  
 If not, is combinating both too much? First we can use the UID, if it's
 not unique then we can start adding, instead of UID, numbers in some
 range? I am probably overthinking it...

 no, the last 6 chars probably aren't unique but I imagine that the last6 +
 test_name + pkgname would be. The odds of having the same test+pkgname
 with 1000000 jobs difference can't be very high.

 But I'm fine with either one. Since we have a staging instance now, I'm
 all for trying it as is (appending 1-5 before giving up and using generic
 UID) for a while and we'll see if we have issues.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:40>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 A week or so ago, I set up a test system with yourls and the current
 incarnation of mkrizek's patch. I had the system up today and figured that
 I would mention this.

 Looking at the links we're generating, I wonder whether we should even
 bother with trying to put the package in the shortened URL.

 For example, the result page:
 {{{

http://autotest/results/505-autotest/192.168.0.173/upgradepath/results/an...
 }}}

 is shortened to:
 {{{
 http://autotest/yourls/0-upgr-noa-anaconda-1619-1fc1
 }}}

 I realize that we wouldn't be using the /yourls/ directory but I'm looking
 at the rest of the shortened URL. Between the lack of '.' and the
 truncated package name, I don't think that's a whole lot more readable
 than the job number or a random string of chars, just longer. How often
 are people really looking at the url to figure out what they're linking
 to, anyways?

 Any thoughts on how we could make this more easily human understandable?
 At the moment, I'm thinking that it might be better to just ditch the
 'custom keyword' option and just go for the UID from yours.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:41>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 Perhaps following could make this a little more human understandable:

 1. Replace '.' with '-', this will result in ambiguous meaning of
 delimiter '-' but will be more readable I think, so for instance:

 http://autotest/yourls/0-upgr-noa-anaconda-16-19-1-fc16

 2. Don't truncate package name to 20 characters, instead leave it as it is
 but use just the first package name (in case 'title' contains multiple
 packages). I am not sure if there are that long package names that would
 result in Bodhi linking it incorrectly again...Or we can combine it and
 use only the first package name and then truncate it to 30-40 characters?

 3. New keyword format: UID-test-arch-fedorarelease-packagename
 Here we could get rid of 'fc[xx]' from all the package names and therefore
 (while combining with 1. for example) have more characters for package
 name.

 The question however is, is this worth it? :) I think any information we
 put in the shortened URL is better than just plain UID.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:42>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Replying to [comment:42 mkrizek]:
>  The question however is, is this worth it? :) I think any information
> we
>  
 put in the shortened URL is better than just plain UID.

 That's what I'm starting to wonder. If the idea is to put these shortened
 links in bodhi comments and emails, there is already enough context to
 figure out what test was run and what packages were involved. I'm not sure
 we really need to make the links human parse-able.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:43>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 Regarding the package names, don't forget our favorite one:
 gnome-shell-extension-alternative-status-
 menu-3.0.2-3.20110630git939994d0.fc15.noarch

 (and all other gnome shell extensions)

 Also, the links will be shortened even for other tests, not just RPM
 tests.

 In these situations we will soon deplete the "uniqueness" and will have to
 fall back to yourls UIDs. We can't base our IDs on autotest job IDs,
 because we can execute several tests inside one job (at least in the
 future).

 I have to admit we probably got lost in the complexity when we might not
 need it at all. I agree with going with plain yourls UIDs for the moment,
 that's very easy to implement. If we don't like it, we can propose
 different approaches in the future.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:44>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by mkrizek):

 The patch is updated (fall back to using UID) as well as ticket347 branch.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:45>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tflink):

 Reviewed. It looks pretty much ready to ship to me.

 Please delete the commented out code for keyword support, though.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:46>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[Kamil Paral]

>  #347: Test results are sometimes linked incorrectly in Bodhi
>  ------------------------+---------------------------------------------------
>   Reporter:  kparal      |        Owner:  tflink
>       Type:  defect      |       Status:  assigned
>   Priority:  major       |    Milestone:  0.7.0
>  Component:  production  |   Resolution:
>   Keywords:              |
>  ------------------------+---------------------------------------------------
>  Comment (by tflink):
>  
>   Reviewed. It looks pretty much ready to ship to me.
>  
>   Please delete the commented out code for keyword support, though.
>  
>  --
>  Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:46>
>  AutoQA <http://autoqa.fedorahosted.org>
>  Automated QA project 
I'd like to review this too, but the whole fedorahosted.org seems down ATM. Tomorrow I
have a training, so I'll look at it on Thursday.

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink  
     Type:  defect      |       Status:  assigned
 Priority:  major       |    Milestone:  0.7.0   
Component:  production  |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by kparal):

 Reviewed.

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:47>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project

[fedora-badges]

#347: Test results are sometimes linked incorrectly in Bodhi
------------------------+---------------------------------------------------
 Reporter:  kparal      |        Owner:  tflink
     Type:  defect      |       Status:  closed
 Priority:  major       |    Milestone:  0.7.0 
Component:  production  |   Resolution:  fixed 
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by mkrizek):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 Pushed: f983f9216eea7e9485b8a1a938a9b1d1ca1ece7a

 I also updated

[https://fedoraproject.org/w/index.php?title=Install_and_configure_AutoQA&...
 documentation].

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/347#comment:48>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project