Just submitted my proposals to ACCU 2012. Only 35 minutes till submission dateline so hurry up. #accu2012

So I didn't go to bed. I created a new Bazaar repository, fired up Emacs, and started typing. To my mild alarm, the ACCU submission procedure this year is all through the web, rather than by emailing in and I almost blew it by misreading the sign up form and having to fill it in again. I hit Submit and read

Thank you for your submission. You may revise your abstract until the submission deadline in 28 seconds.

Making Jenkins Better

Jenkins is a widely used and extremely capable continuous integration server. While it's been available since 2007, under it's original name of Hudson, its popularity seems to have really taken off in the past year or so. One of the primary reasons for its success is it's extremely flexible configuration. Jenkins has a quite a small core, with most of its functionality provided through plugins. Jenkins' plugins provide access to different source code control systems, a wide variety of build tools, test result tracking and charting, static analysis tools, and so on. Nearly every aspect of Jenkins can be customised via a plugin. At time of writing there are over 400 different Jenkins plugins available.

Four hundred is too few.

Over the past two years, we've gone from dabbling with CI to Jenkins forming part ofour core toolset. Jenkins builds on checkin, yes, but also deploys builds into development environments. It runs performances tests and records the history. It tells us which build contains which bug fixes. It also does our release builds - tagging the repository, building from the tag, writes release notes telling us which work packs have been updated, pushes the build up onto the live server, and emails Ops to say everything is ready to go. The standard plugins provide the foundation, but the our own plugins have put Jenkins at the heart of our development process.

If you want to get the most from Jenkins, you really should write your own plugins. This session will explain why you should, what you can change or add to Jenkins, and how to do it.

The code is more or less constantly evolving, so there are often new features or bug fixes in the code some time before a release to the Android Market. Features or bug fixes you might like to have. Of course, not everyone has the time or skills to build the code themselves. Fortunately, we have software to that for us.

Each time I make a change to my copy of the app's code, a new build of the app will appear here. Whatever I'm working on might not be entirely complete, but it'll be the very latest code there is.

Once I have finished a feature, I push the code into the main branch. Those builds will appear here, in the master directory. Builds of this branch will happen less often, but new features should be complete.

To install any of these builds, you will first need to uninstall any existing version of the CycleStreets app you might have on your phone, and then turn on the "Unknown sources" setting. With that done, download the build and, once the download completes, select it. Your phone should offer to install it.

Unfortunately, there's no way to automatically update an application you've downloaded like this. The best I can offer is an RSS feed of builds.

I picked up this project at the start of the year, when it was essentially dormant, and now it's live just in time for Bike Week. Read more about it on the CycleStreets blog or poke around in the code on GitHub.

 undefined reference to
`std::basic_streambuf<char, std::char_traits<char> >::seekoff(long, std::_Ios_Seekdir, std::_Ios_Openmode)

• Check out the LLVM & Clang source and build it as described on the Clang website.
• Open up ~/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp in your favourite text editor.
• Add the following at line 627, just under the case for llvm::Triple::Linux

      // Ubuntu 10.10 "Maverick Meerkat" -- gcc-4.4.5 
      AddGnuCPlusPlusIncludePaths("/usr/include/c++/4.4",
                                  "i686-linux-gnu", "", "64", triple);
  

• Build again. It'll be much quicker this time around.
• Install - sudo make install

With any luck Clang will be patched up in pretty short order, thus rendering this a historical curiosity.