Benjamin Niemann wrote: > Hi again, > > ok, I got something working. Tests and pylint messages integrate nicely. > The way the build script finds the jar is hopefully stable enough to > not break too often. And for the antlr2 and st dependency I just > download (if not already done) and install them in the workspace as > part of the build. > > Can someone with the appropriate admin powers please setup a Hudson > account for me, so I can configure my job? > > How should I setup the P4 client for the Hudson workspace? Is there a > naming convention for the client name? And which user to use? My own > account, which I wouldn't like, because then my password is in > cleartext on the server. Or is there a dedicated (readonly) hudson > user? > > And finally: the build script need pylint. If not yet present on the > host, it has to be installed. "apt-get install pylint" or the > equivalent of your distribution. I assume that python is already > installed. Would also be nice if multiple python versions (2.4 > upwards) could be installed, so .egg files for each version can be > build - the build script will auto-detect all versions present in > /usr/bin/. > Send me all the stuff - it is probably quicker for me to create the job than explain all the ins and outs of the perforce plugin and so on. I will install pylint etc. Note that you can probably just send me your .hudson folder as a tar, then the scripts you have written.
Jim _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
