Re: [tycho-dev] An Hudson Instance for Tycho + Sonar analysis?

[Mickael Istria <mistria@xxxxxxxxxx>]

On 09/23/2013 09:41 AM, Sievers, Jan wrote:

The current build jobs work for me and I spent quite some time to get them to the current state.

Frankly, moving build jobs around manually and working on patching them until they work again as they did before is not on the top of my prio list.

I don't think there is any need to patch the jobs. At least it was transparent to move SWTBot from the 2 hudson instances to its HIPP one. HIPP has same settings and permissions than the current Hudson instance.
Moreover, when setting up the Hudson Instance for the project, jobs are not deleted on the current Hudson instances but just disabled. So it's easy to roll-back in case of issue.
Job configuration are copied from the common Hudson to the project one.

 Any links to what "HIPP" is and why we should move our builds there?

It was advertised by Denis on the cross-project list. It's just the ability to get all project jobs in a single Hudson Instance dedicated to this project. With additional permissions given to the committers. The best reference I found so far is https://bugs.eclipse.org/bugs/show_bug.cgi?id=403843 . You can see what it looks like at
* https://hudson.eclipse.org/swtbot/
* https://hudson.eclipse.org/platform/
and many other URLs of this kind.

The benefits are that there is a single place where to look for CI jobs. It makes it easier for a contributor to have an overview of the builds available. It also make it easier to say to people "look at the CI job for more details" because everything is at the same place.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets