Last modified: 2014-07-03 13:13:07 UTC
https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.org-linux-firefox/rssAll and https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.org-linux-chrome/rssAll are not public. This means Selello [1] - a tool that Mobile team uses to create Trello cards for broken builds will not work. Please fix! [1] https://github.com/wikimedia/bingle
Jenkins is fundamentally screwed with our current setup. Whenever the RSS URLs are accessed it will attempt to parse all the build history to figure out the status of builds. Since we have bot crawling the web page from time to time, I had to blacklist them at apache level (filled out privately in bug 61964). Jenkins has a json API but it suffers from the exact same issue. Jenkins is quite powerful on other aspects though and could be made to run your utility after the build is complete. That would probably be a bit more robust. Another approach would be to use the json API to figure out the latest build: https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.org-linux-firefox/api/json?pretty=true&tree=lastBuild[number] That yields: { "lastBuild": { "number": 88 } } Then use that build number to retrieve the test results: https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.org-linux-firefox/88/testReport/api/json?pretty=true Or get the whole build result and format it to build the card: https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.org-linux-firefox/88/api/json?pretty=true Any work made on that front can later be reused for Phabricator I guess.
Okay, I tried to use the JSON api. It's probably a better move on long term. https://github.com/wikimedia/bingle/pull/40 Shame the RSS feed doesn't work though...
RSS is not going to be reenabled. Seems the utility has been migrated to Jenkins JSON api. So I am assuming this bug is no more needed.
