首先,将鼠标悬停在下面的灰色区域。不是答案的一部分,但绝对不得不说:
If you have a shell script that does “checkout,build,deploy” all by itself,then why are you using Jenkins? You are foregoing all the features of Jenkins that make it what it is. You might as well have a cron or an SVN post-commit hook call the script directly. Jenkins performing the SVN checkout itself is crucial. It allows the builds to be triggered only when there are changes (or on timer,or manual,if you prefer). It keeps track of changes between builds. It shows those changes,so you can see which build was for which set of changes. It emails committers when their changes caused successful or failed build (again,as configured as you prefer). It will email committers when their fixes fixed the failing build. And more and more. Jenkins archiving the artifacts also makes them available,per build,straight off Jenkins. While not as crucial as the SVN checkout,this is once again an integral