| pivotal | Thanks, cjwatson. acheronuk, we'd like to consume the build success/failure with a script in our CI system (green/red). Both success and failure could be scraped from the PPA web site, I suppose. | 00:41 |
|---|---|---|
| wgrant | pivotal: No need to screenscrape. There are APIs for what you need. | 00:44 |
| wgrant | eg: | 00:44 |
| wgrant | In [5]: [b.title for b in lp.archives.getByReference(reference='~launchpad/ubuntu/ppa').getBuildRecords(build_state='Failed to build')[:2]] | 00:44 |
| wgrant | Out[5]: | 00:44 |
| wgrant | [u'amd64 build of pg-repack 1.4.2-1~ubuntu16.04.1~ppa1 in ubuntu xenial RELEASE', | 00:44 |
| wgrant | u'i386 build of pg-repack 1.4.2-1~ubuntu16.04.1~ppa1 in ubuntu xenial RELEASE'] | 00:45 |
| wgrant | Those are the two most recent failed builds in the PPA for Launchpad itself. | 00:45 |
| acheronuk | pivotal: yes, but as above. for example Kubuntu uses the API to get build status/logs etc for our QA status pages such as http://qa.kubuntu.co.uk/ppa-status/applications/build_status_17.08.3_bionic.html | 00:47 |
| acheronuk | or our CI does it for our development builds | 00:48 |
| pivotal | Cool, thanks, looks like that python helper is at https://help.launchpad.net/API/launchpadlib , wgrant? | 00:55 |
| wgrant | pivotal: Yep. If you're on Ubuntu, you can install lptools and ipython and run "lp-shell production devel" to fiddle around with it | 00:57 |
| === ePierre-afk is now known as ePierre | ||
| === ePierre_ is now known as ePierre | ||
| === ePierre is now known as ePierre-afk | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!