Community
Participate
Working Groups
Invoke builds from web ui authenticated by eclipse committer rights with parameters - maintenance build vs i-builds, tests or not etc.
I've been testing hudson (https://hudson.dev.java.net/) for the past few days on our local build machine. It seems to be working quite well. I had to change the build so the bootstrap script it fetched from cvs instead of just invoking the script on the filesystem. It also has facilities to run parse the JUnit results and provide graphical history of test results which could be useful. Other changes that are required. -change generated hudson build id to match the convention that we use for our builds -move bootstrap bundle to eclipse.org cvs -add authentication to access hudson The long term plan is to be able to move to the hudson server on build.eclipse.org once all the details have been worked out. See bug 257265.
Created attachment 142929 [details] initial patch, there will be many more :-)
*** Bug 61897 has been marked as a duplicate of this bug. ***
Created attachment 143549 [details] add ant variable to indicate if build is running on hudson
Created attachment 143692 [details] patch to change director invocation from exe to launcher jar
The patch in comment #5 is bogus, the director can't be in a forked vm, this results in an IllegalStateException with a message "The profile is currently in use".
Other issues to fix: -move properties files that are used by compareMaps to a common location that's writeable by the hudson build user. -change rsync order to push directly to download.eclipse.org
*** Bug 255817 has been marked as a duplicate of this bug. ***
Created attachment 144844 [details] director patch
Created attachment 146455 [details] patch to use basebuilder class when updating test results page
There is a a successful test build here. I didn't sign or pack it since I was testing it, and this slows things down. https://build.eclipse.org/hudson/job/eclipse-equinox-test/59/ Other tasks to fix -need to have a separate cronjob to copy the artifacts, php etc to download directory on download.eclipse.org. The hudson user doesn't have commit rights to any of these directories. -need to copy the existing p2 repo over to use as a baseline. Currently, it just creates a new one. -need to figure out how to tag each build so it can be reproduced. Again, this is because the hudson user doesn't have commit rights. -After this is implemented, I can look at the changing the way the tests are run so that they are run in the cloud. -Also, it would be good to make the build more modular and chain the build together. For instance, I could build the master feature and make a repo. That may be sufficient for some people to test their bundles. Others may want to try build the SDK -I added the eclipse-all group to this test job so other committers could try it out for test builds. It can be invoked here.... https://build.eclipse.org/hudson/job/eclipse-equinox-test/
Created attachment 147478 [details] patch to change use http baseline with hudson
I just ran an unsuccessful test build with signing and packing enabled on hudson. It seems that the pack step is failing silently and thus the metadata is not updated with the correct artifact sizes post packing. Investigating....
Eclipse and Equinox committers can run tests builds on build.eclipse.org. (eclipse-all group has permissions to start a build) https://build.eclipse.org/hudson/job/eclipse-equinox-test/ Login is your committer id and password. This test build isn't replicated to download.eclipse.org. You'll see any errors in the console log on the hudson build page for this build type. This build doesn't run tests, this is being investigated in bug 247320.
It looks like the compile logs view in Hudson isn't generated until the build completes successfully. We don't publish bundles with compile errors to the repo. Thus the build will fail when the director is run and the compile errors won't be reported without digging through the build files. It would be good to email the compile errors to specified recipients. It doesn't look like the hudson's ext email support provides this functionality at this time.
You can watch the logs as the build proceeds.
I think this can be closed since eclipse Hudson builds not have this restriction.
Previous comment was for another bug. I think this can be closed, consolidating the bugs for this issue in the 3.7 plan item, bug 325997. *** This bug has been marked as a duplicate of bug 325997 ***
