Community
Participate
Working Groups
Or possibly reuse web ui provided by other projects such as hudson etc, so we aren't forced to maintain ui on an ongoing basis
The more I play with Hudson, the more I love it. It seems to have everything that CruiseControl has, plus so much more. Compare: CC: http://build.eclipse.org:9777/dashboard/tab/build/detail/ganymatic-R3.0-I/20081103131140 Hudson: http://hudson.jboss.org/hudson/view/JBossTools/job/jbosstools-nightly/ http://hudson.gotdns.com/wiki/display/HUDSON/Home Maintaining my old custom web UI seems like an exercise in pain, when there's a much better solution out there. Once we're done w/ the commandline/ant-script invocation of the CBI build system, we can turn our focus to version control monitoring for change-based, scheduled, and continuous builds. Hudson also supports the idea of fingerprints and builds that kick other builds. https://hudson.dev.java.net/fingerprint.html
that sounds like an interesting approach. BTW, I can't reach http://build.eclipse.org:9777/
First prototype CBI build via Hudson UI: https://build.eclipse.org/hudson/view/Athena CBI/job/cbi-gef-3.4.x-nightly/ Works great, except for signing. See bug 264633. I guess all that's left for this bug is documentation as to how to use Hudson. The simplest approach is to copy the existing build config and create a new one from it, then modify it to suit the user's needs. Beyond that, I expect all the docs we'll need are inline within Hudson or on its website.
Dude, this is awesome! Nice work.
Yes it looks great! What is the "Eclipse Logon" I was asked for when clicking around? Is the my shell login or Bugzilla?
It's your committerid login, as used for the portal (I'm nickb). You need to be in the callisto-dev group, too. I expect the reason for this is that Hudson only available for projects involved in the annual Release Trains in order to encourage participation and coordination, and of those projects, only those committers already used to release engineering processes and responsibilities.
As signing is now working, I'm closing this bug. Additional information in http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started
