> I meant that committers from other Apache projects could help us out > as Jenkins admins (not just Pivot committers), and anyone could help > on the mailing list or by watching the RSS feeds to see if they can > help with any problems that might come up. Yes, I'll try to ask to someone, maybe with a cross-post ...
>> On build files, if possible I'd prefer to not duplicate them ... now >> let's see if it will be possible without doing too much changes. > As long as Jenkins related changes don't break the existing scripts > (or add any extra dependencies) then it is fine. > > I just want to make sure that changes to the build files now won't > cause any problems for the 2.0.1 release, or for anyone checking out > the SVN tree and attempting to build. Yes, I agree, so in the meantime I will not commit anything related to this change. >> For example, I'm searching how to let jenkins find the junit jar and >> other jdk jars required by us, but the only thing I can do on jenkins >> apache servers is using some already existing environment variables, >> because physical path on servers there probably can change, and >> probably I can't even read files outside our workspace there (so I >> can't point to junit jar like adding it in ant target like: -lib >> /usr/share/java/junit4.jar ). >> In the worst case I think we could put required jars (assuming that >> the license permit it) in a deidcated ci folder inside our trunk >> (because it get all from SVN, starting from this folder) ... let's >> see. > I'll try to take a look a little bit later today. Obviously things > like JUnit will be used by lots of other builds, so it should be > fairly easy to set up those more common jars. The SVG and servlet > jars are already included in the SVN tree, but the plugin one is not. > I imagine that should be easy to locate the JDK's path if there is an > environment variable pointing to it. Yes, probably jdk jars should not be a problem, there is a JAVA_HOME env var. But the problem seem with JUnit, I'm looking even in other Jenkins projects there but until now no more info ... and the problem seem the JUnit has a license NOT compatible with the Apache license (this is the reason we don't include it directly in our build and workspace). So I'll continue to search for info, and ask even to apache legals, to see if it's a problem already solved (I think it is). Let's see later. Bye
