Hi Michael,
I went to take a look at the kernel ci-loop page to see the build status of upstream builds and have a few new comments on the UIL
1) When there is a build failure, is it possible to have the build link go directly to the build results? It currently takes 3 clicks to get to the results from the main page and it may not be obvious to someone that the "consoleText" attachment is the correct link to use.
2) From the main ci-loop page, how do I get to a link for the RSS feed? Are the RSS feeds per-tree or per (tree + defconfig) combination? The later is preferred from the perspective of having upstream sub-arch maintainers who want to watch specific platforms.
Thanks, ~Deepak
On Tue, 8 Nov 2011, Deepak Saxena wrote:
Hi Michael,
I went to take a look at the kernel ci-loop page to see the build status of upstream builds ...
FYI, the venerable ARM kautobuild run by Vincent Sanders was shut down a while ago.
http://article.gmane.org/gmane.linux.ports.arm.kernel/139303
This means there is now a real hole to fill. Given that Linaro's ci infrastructure has more resources, it hopefully will be more useful too. One thing that I didn't like much about kautobuild is that it only coalesced all build results into a single report instead of having a per config failure report sent to the appropriate maintainer.
Should we try to advertise Linaro's plans more widely?
Nicolas
On 8 November 2011 14:10, Nicolas Pitre nicolas.pitre@linaro.org wrote:
On Tue, 8 Nov 2011, Deepak Saxena wrote:
Hi Michael,
I went to take a look at the kernel ci-loop page to see the build status of upstream builds ...
FYI, the venerable ARM kautobuild run by Vincent Sanders was shut down a while ago.
http://article.gmane.org/gmane.linux.ports.arm.kernel/139303
This means there is now a real hole to fill. Given that Linaro's ci infrastructure has more resources, it hopefully will be more useful too. One thing that I didn't like much about kautobuild is that it only coalesced all build results into a single report instead of having a per config failure report sent to the appropriate maintainer.
Should we try to advertise Linaro's plans more widely?
What I'd like to do is get this being used regularly by Arnd and also the TI maintainers first (as they've expressed some interest in it). Once that's up and running, we can reach out to other sub-architecture maintainers and figure out which trees/configs we want to build. I'd rather get the kinks sorted out with a small group than opening up to lots of people at once.
~Deepak
Nicolas
On Tue, 8 Nov 2011, Deepak Saxena wrote:
On 8 November 2011 14:10, Nicolas Pitre nicolas.pitre@linaro.org wrote:
On Tue, 8 Nov 2011, Deepak Saxena wrote:
Hi Michael,
I went to take a look at the kernel ci-loop page to see the build status of upstream builds ...
FYI, the venerable ARM kautobuild run by Vincent Sanders was shut down a while ago.
http://article.gmane.org/gmane.linux.ports.arm.kernel/139303
This means there is now a real hole to fill. Given that Linaro's ci infrastructure has more resources, it hopefully will be more useful too. One thing that I didn't like much about kautobuild is that it only coalesced all build results into a single report instead of having a per config failure report sent to the appropriate maintainer.
Should we try to advertise Linaro's plans more widely?
What I'd like to do is get this being used regularly by Arnd and also the TI maintainers first (as they've expressed some interest in it). Once that's up and running, we can reach out to other sub-architecture maintainers and figure out which trees/configs we want to build. I'd rather get the kinks sorted out with a small group than opening up to lots of people at once.
I was thinking more about letting people know what we are up to, not necessarily open the system to anyone yet.
Nicolas
On Tue, 8 Nov 2011 12:56:39 -0800, Deepak Saxena dsaxena@linaro.org wrote:
Hi Michael,
I went to take a look at the kernel ci-loop page to see the build status of upstream builds and have a few new comments on the UIL
- When there is a build failure, is it possible to have the build link go directly to the build results? It currently takes 3 clicks to get to the results from the main page and it may not be obvious to someone that the "consoleText" attachment is the correct link to use.
Yeah, this is pretty terrible currently. It's already reported though: https://bugs.launchpad.net/lava-kernel-ci-views/+bug/876010
- From the main ci-loop page, how do I get to a link for the RSS feed? Are the RSS feeds per-tree or per (tree + defconfig) combination? The later is preferred from the perspective of having upstream sub-arch maintainers who want to watch specific platforms.
The only RSS feeds we have right now are from Jenkins, so start at: https://ci.linaro.org
Cheers, mwh
On Wed, Nov 9, 2011 at 5:36 AM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
On Tue, 8 Nov 2011 12:56:39 -0800, Deepak Saxena dsaxena@linaro.org wrote:
- From the main ci-loop page, how do I get to a link for the RSS feed? Are the RSS feeds per-tree or per (tree + defconfig) combination? The later is preferred from the perspective of having upstream sub-arch maintainers who want to watch specific platforms.
The only RSS feeds we have right now are from Jenkins, so start at: https://ci.linaro.org
We have some documentation on how to subscribe to build failures here:
+ https://wiki.linaro.org/Platform/Infrastructure/LinaroCI/RSSForBuildFailures
This includes subscribing to a complete tree as well as to a particular tree/defconfig/
-
Alexander Sack -
Deepak Saxena -
Michael Hudson-Doyle -
Nicolas Pitre