1. Add a bug to a failing jenkins job by editing the description of that run (with the format of 20130227,LP:#1134162)
2. Publish the job again and the bug should be visible in http://reports.qa.ubuntu.com/smoke/precise/flat/ when the dash does a rescan. But sometimes it does not happen.
Some bugs that are tagged to the failing jobs do not get parsed to http:// reports. qa.ubuntu. com/smoke/ precise/ flat/ and do not appear there.
So basically,
1. Add a bug to a failing jenkins job by editing the description of that run (with the format of 20130227, LP:#1134162) reports. qa.ubuntu. com/smoke/ precise/ flat/ when the dash does a rescan. But sometimes it does not happen.
2. Publish the job again and the bug should be visible in
http://
For e.g. the view reports. qa.ubuntu. com/smoke/ precise/ run/2323/ image/2323/
http://
does not have the bug that's added to the description of the failing job /jenkins. qa.ubuntu. com/job/ precise- desktop- amd64_oem/ 486/
https:/
and reports. qa.ubuntu. com/smoke/ precise/ run/2324/ image/2324/ /jenkins. qa.ubuntu. com/job/ precise- desktop- i386_oem/ 521/
http://
does not get the bugs in
https:/
Although not confirmed, I seem only to notice this issue with the jobs for precise.