On 05/03/2015 06:53 PM, Elfy wrote:
Prior to the vivid cycle I used to often check on jenkins daily,
indeed had RSS feed for fails set up, just to check that things were
at least working basically.
Sometime around December these stopped working, and still show the
last result as about 5 months ago as FAIL for everyone.
Is there any likelihood that this will work for us during the Wibbly
Wobbly Whinocewos cycle?
Is there somewhere else that reports on both Ubuntu and flavour image
auto tests?
I know this would make my life just that bit easier, I assume other
flavours would like to at least have the assurance a basic test is done.
Elfy, we spoke before about checking the RSS feed and posting it to the
isotracker. I still owe you an attempt at that. Can you link what you
are looking at?
This should work and show things properly; it's the smoke tests:
https://jenkins.qa.ubuntu.com/view/vivid/view/Smoke%20Testing/
On the AP test side, CI took down the machine on accident and stopped
the builds. They've since restored them, but only for ubuntu:
https://jenkins.qa.ubuntu.com/view/Ubiquity/view/All/
There's an open work item from me to restore them for other flavors, but
we would be better served thinking of an alternative place to run them I
think and pursuing your idea of publishing failures on the tracker
itself as a warning. Ideas anyone?
Nicholas
--
Ubuntu-quality mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
