Responses inline.
-Eric
On 12/29/2012 10:50 AM, Paulo J. Matos wrote:
On 24/12/12 16:41, Eric Pyle wrote:
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.
Thanks. What do you mean 'another Jenkins job'?
Like creating a new shell script that is called by the build script?
No, I mean a separate Jenkins job, with a different name. For example,
if you have a piece of software called "project1", you might have two
jobs: project1_build and project1_tests. Job project1_build would check
out and build the source code for project1, including any unit tests.
Job project1_tests would check out system-level tests (tests that call
the compiled software to perform certain tasks).
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.
Is there an option to do that with git plugin in jenkins? I can't find
anything.
I am new to git myself so I'm not an expert on this, but I think there
is a way to do it.
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.
Thanks.
Regards,
Eric
On Mon, Dec 24, 2012 at 8:02 AM, Paulo J. Matos <pa...@matos-sorge.com
<mailto: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.com
<mailto:eric.p...@cd-adapco.com>
www.cd-adapco.com <http://www.cd-adapco.com/>
CD-adapco logo and social media buttons
