2011/7/3 Rupert Westenthaler <[email protected]>: > Hi > > The problem is that we (again) run into the 1h timeout for the Builds > of the jenkins server. This is mainly because the building of the > launchers take so much time (e.g. 19min for the stable launcher for > build 274). In the middle of building the full launcher the timeout > occurred. In such cases the UI does not stop the time taking for the > canceled task. Because of that it notes that the build process of this > tasks takes for ever. > > I see only two possibilities: > > * Somehow increase the timeout (how to increase the timeout?)
I don't think this is a good idea anyway. Building and testing should take less than an hour otherwise we will get the broken build results too late. > * only include the full launcher in the build executed on the Jenkins > server (how to exclude specific tasks from the build used by the > Jenkins server) We could put specific maven profile on the other integration test so that we would have to make it explicit that we want to build / run them with "mvn clean install -Pstable" for instance. However I don't understand why it takes such a long time on jenkins. On my box a full build + test takes 17min and the launchers test run respectively in: [INFO] Apache Stanbol Launcher - Stable ...................... SUCCESS [44.255s] [INFO] Apache Stanbol Launcher - Stateless ................... SUCCESS [29.823s] [INFO] Apache Stanbol Launcher - Full ........................ SUCCESS [57.633s] [INFO] Apache Stanbol Integration Tests ...................... SUCCESS [2:34.210s] On jenkins, the 2 launcher builds that have the time to finish take a much longer time: Apache Stanbol Launcher - Stable 4 min 42 sec Apache Stanbol Launcher - Stateless 19 min Any idea? On my box I have: $ echo $MAVEN_OPTS -Xmx1g -XX:MaxPermSize=512M Maybe we could increase this for jenkins? -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel
