Hi Paulo, I think common practice is to have your shell script build when it detects a check-in via polling, on successful completion of build it would call another Jenkins job to install and test. This separates pure compiling errors from logical or other errors which cause tests to fail. Second, although you can have a build directory outside the workspace, I would not recommend it. You can set up your SCM checkout to go into a subdirectory of the workspace if that seems better. On your third question, Jenkins will not automatically delete the workspace after a job completes. You should keep at least the most recent build's workspace in case it is needed to diagnose issues with the build or install/test. Jenkins can be configured as to how many past builds are kept and whether to clean the workspace prior to starting a new build.
Regards, Eric On Mon, Dec 24, 2012 at 8:02 AM, Paulo J. Matos <pa...@matos-sorge.com>wrote: > Hello, > > I am using jenkins for the first time. > Great software, I am very happy with its ease of use. > > I do however have some questions: > * I got jenkins to hourly poll a git rep, the I execute a shell script. Is > this shell script supposed to build, install and test? Or should these > things be separated into different scripts? > * The workspace seems to be the git repository root; Can I have the build > directory and install directory outside the workspace? > * Should I remove the build and install directories afterwards or will > jenkins take care of that? > > Is there a way to receive an email also containing the new changes to the > repository? > > Thanks, > > Paulo Matos > > -- *Eric Pyle *Build Manager CD-adapco - Lebanon, NH Office +1 603-643-9993 x24161 (T) +1 603-359-8670 (M) eric.p...@cd-adapco.comwww.cd-adapco.com[image: CD-adapco logo and social media buttons]
