Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let's see the tasks you want to do...</p> <blockquote> <ul> <li>update directory (svn update)</li> </ul> </blockquote> <p>Well, Jenkins will do that anyway.</p> <blockquote> <ul> <li>compile</li> </ul> </blockquote> <p>And, that too...</p> <blockquote> <ul> <li>run tests</li> </ul> </blockquote> <p>Why not? Jenkins can display the JUnit tests results right on the build page. If the tests take a really long time to complete, you can setup a second job to do the tests. Have Jenkins copy the working files from the old job to the new job, and run the second job. There's a <a href="https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin" rel="nofollow">Copy Artifacts</a> plugin that will help you do this.</p> <blockquote> <ul> <li>make coverage report</li> </ul> </blockquote> <p>Jenkins can do that too. And, just like the JUnit tests, Jenkins can display the results on the build page.</p> <blockquote> <ul> <li>run static analyzers and generate reports.</li> </ul> </blockquote> <p>Jenkins can do that too.</p> <blockquote> <ul> <li>package (make war-file)</li> </ul> </blockquote> <p>Jenkins can do that. You can even store the war file on Jenkins. People will be able to copy it and deploy it on their systems. Or, you can have Jenkins store it in your Maven repository. Heck, you can do both.</p> <blockquote> <ul> <li>deploy to a web-server</li> </ul> </blockquote> <p>Jenkins can do this, but I prefer to do this manually -- unless there's some testing I want to do as part of the build process. When it comes to deployment, I'd rather do things myself.</p> <blockquote> <ul> <li>send email notifications (with linked reports and build status)</li> </ul> </blockquote> <p>Standard Jenkins is to send out notifications on bad and <em>unstable</em> builds (builds that built, but where tests failed), then send an email once the build is good again. Do you really want an email sent out with each and every build? If so, use the ext-mail plugin.</p> <blockquote> <ul> <li>run DB update tool</li> </ul> </blockquote> <p>Again, this is something I prefer to do manually -- unless this is part of my testing.</p> <blockquote> <ul> <li>put a build result (war file and reports) to a special place</li> </ul> </blockquote> <p>No need to do that. The Jenkins individual build webpage itself can store the war file, the testing results, who started the build, and what was changed. The changes can be linked to Fisheye, Sventon, or another source repository web browser which allows a user to click on a file and see exactly the lines changed.</p> <p>Jenkins also has a permanent link to the last good build, the last bad build, and the last build. I use iframes (Bad David! Using obsolete HTML code) to embed these pages in the official corporate web pages.</p> <p>In short, Jenkins can do all of that stuff for you, so why not let it?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload