Hi, I've looked through our jenkins jobs at [1]. Here are a few tips:
1. don't configure build jobs with -DskipTests. I've seen some of our components configured this way. The whole point of CI is to get feedback about changes. This includes test results. 2. configure the build to run after SCM changes. None of the projects I've looked into is configured to run automatically after SCM changes. There is a checkbox in the lower half of the job configuration to let where you can at a cron exrpession for polling the SCM. I've configured @hourly for [lang], [csv] and [imaging]. 3. Use the right Maven version. It looks like some of the preinstalled maven versions don't work on all machines. I've configured the components I've looked into to use maven-3.3.5. The Maven versions with name pattern 'Maven x.x.x' oder 'Maven x (latest)' don't seem to work. Regards, Benedikt [1] https://builds.apache.org/view/Apache%20Commons/
