Hi folks, I wanted to clarify how builds work in Jenkins, at https://ci.gitorious.org/jenkins/
Each of the jobs are set up as "multi-configuration" projects. I set things up this way so that we could test the builds on multiple platforms. For example, we started out on CentOS 6 with the standard Ruby 1.8.7. Later on, I added a build slave with CentOS 6 and Ruby 1.9.3. Down the road, we can add CentOS 7 (with Ruby 2.0) when the CentOS project releases their OS. We can also add in other build slaves - for example, Debian or Ubuntu. The one "gotcha" with multi-configuration builds is that it's not exactly intuitive to read the results of the test suite. Here's how to access that information. ---------- Let's say we click on "mainline" - this is the main Gitorious project. This takes us to the URL https://ci.gitorious.org/jenkins/job/mainline/ On the left there is a "Build History" window, with all the recent builds. I'll click on the "Dec 13, 2013" one. https://ci.gitorious.org/jenkins/job/mainline/126/ At this point, the natural inclination is to click on "Console Output". Unfortunately that is not the proper link. If I click on that, it will just show me the output of triggering on the SCM changes that went into mainline yesterday. https://ci.gitorious.org/jenkins/job/mainline/126/console The clue is down at the bottom of this text: Triggering centos-6-ruby193 centos-6-ruby193 completed with result SUCCESS That is the actual build slave that ran the tests - this is what we really want to access. I'll hit "back" in my browser to go to the main build page for December 13th https://ci.gitorious.org/jenkins/job/mainline/126/ again. There's another section on this page, titled "Configurations", down at the bottom. Right now there's just a single configuration, which Jenkins calls "Default". When I click on that, then I see the the actual build on the Ruby 1.9.3 build slave. https://ci.gitorious.org/jenkins/job/mainline/126/label=centos-6-ruby193/ The "label=centos-6-ruby193" bit in the URL is important. Now I can click on "Console Output here, and it shows me the full text of the build. https://ci.gitorious.org/jenkins/job/mainline/126/label=centos-6-ruby193/console In summary, be sure that you're viewing the proper configuration for a job - otherwise the top-level console output for a job won't be particularly helpful. The extra step of clicking on the "Default" configuration is important. (I think this is one of the more non-intuitive parts of navigating Jenkins.) - Ken -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
