Infrastructure – LogSaw Project

On the benefits of the Maven switch

philippn — Wed, 19 Dec 2012 00:33:58 +0000

One of the really cool things about Maven is how well-supported it is. Ironically, I realized this while trying to figure out how to solve a bug in Maven-Tycho.
Long story short: My build machine at home is running Windows and that is causing troubles with Tycho doing cross-platform builds on it.

For several reasons, switching the OS is not an option for me and so I went on looking for alternatives. I came across CloudBees, which — as their company name suggests — are offering a bunch of services in the cloud. Most notably, a free Jenkins instance.

The service works suprisingly well so far. And thanks to the power of Maven, setting it up was a breeze. A picture tells a thousand words

CloudBees Jenkins instance

Building instructions updated for Maven-Tycho

philippn — Sat, 29 Sep 2012 10:45:38 +0000

I have finally updated the building instructions page for the new Tycho-based build process. There are still some outstanding issues with this new build process though:

p2.inf touchpoints are not picked up anymore
version and build number expansion doesn’t work anymore

But I think these remaining issues should be fixable with reasonable effort.

Migration to Maven-Tycho

philippn — Tue, 24 Jul 2012 22:51:00 +0000

Tonight, I have started migrating the build infrastructure behind LogSaw from Buckminster to Maven-Tycho. Please note that you may experience weird problems until all kinks are sorted out. I will keep you posted.

Build infrastructure changes

philippn — Sat, 22 Oct 2011 15:53:11 +0000

First of all, sorry for the slow updates! I’ve been quite busy lately, and LogSaw already does pretty much all I need, so the pressure for me to make changes has been quite low. Though, it’s still all alive and development should continue soon

I have been playing around with Buckminster some more recently, and I ended up making the whole development process alot easier (did I already mention, that I really like Bucky?). So, if you ever wanted to play around with the LogSaw source yourself, but were unsure on how to get started: The new Building LogSaw tutorial should help you to get started.

Switch to Git SCM completed

philippn — Wed, 16 Mar 2011 23:22:45 +0000

I have just completed moving the source code to Git SCM. The master repository is now hosted on GitHub. However, a clone of it is also hosted on SourceForge because it doesn’t allow to point to an external Git repo only.

Then again, Git is very capable in terms of syncing multiple repos so this shouldn’t be much of an issue