This way people could easily test the current code, we just have to put up some visible links to it.
Nightly builds for windows and osx sound like a nice idea. Maybe we should use 2 additional Jenkins jobs (1 for Windows, 1 for MacOs) that only checkout/compile/jar the current trunk (no unit testing, findbugs run...).
As I'm still new to maven, I'll need some support to configure the correct maven goals.
Could you tell me the mvn command to generate the packages for windows and mac (without running the platform specific build tools)?
taconaut wrote:If you can host other forks, I'd love to see pms-mlx there too.
I've setup a job for pms-mlx but getting an build error. I can reproduce the problem on my local linux box.
I've temporarily increased the git polling time to every 15 minutes, so you should get results fast if you trying to fix the issue..
taconaut wrote:Isn't space and bandwidth an issue?
Space is not a problem at the moment. Builds older than 30 days are deleted by Jenkins. Do you think this is enough?
Bandwith isn't an issue for additional build jobs. However, I'm not sure how many user will download daily builds and generate traffic. But we can give it a try. As a fall back Jenkins could be configured to upload the nightly builds to another download site..