2012/2/22 fiona <bingxue0...@hotmail.com>: > I confused about svn revision policy in system configuratioin. my > understanding as follows: > queue time: if I set Poll CM to */10 * * * *,when ten minutes > arrive,i.e. 10:50:40,my WC will update to the revision at the > time ,even the build is waiting for long time in queue ?
WC? You mean workspace? No. Even if Jenkins checks your svn server, it does not change the workspace of a build that is running. > build time: when ten minutes arrive, if the frontal build do not > finish, then the build will be in queue, so when it startup ,maybe it > is delayed for many miniutes, the revision will be at the time it > startup? When a build actually starts, it will check out whatever is the latest version at that moment in your version control. > Head revision : whenever the build startup, the revision is the latest > at the time the build startup? Isn't this the same question as above? I'm sorry if I misunderstood. English is not my native language. > my understanding is right? my best confused is Head revision, if the > revision is the latest at the time the build startup, I find it update > to the revision after the startup time,why? I'm sorry... I must still be misunderstanding. It makes sense to build using the latest version. Otherwise you would need to make another build to test the latest version. If you want to implement continuous integration to build _every commit_, you need to create an SVN hook script that triggers Jenkins to build a specific commit. Usually people do not want to build every commit, because building+testing takes a long time. -- Sami
