Hello Jenkinsians,

I have a rake build script, which I just tested.

The build script:
 * zaps the build folder [ d:\Builds\MyProject ]
 * recreates a pristine build folder
 * gets the exported source from subversion
 * builds it
 * copies the result to two project folders:

        d:\Builds\MyProject\Admin
        d:\Builds\MyProject\Client

On the same drive there are two website folders I eventually want to
copy this to (but the build currently does not do that):

        d:\Domains\Admin
        d:\Domains\Client

I need to
* poll the repository for updates.
* run the build script on finding an update, check the status of the
build script after it's terminated.
* copy my new websites over if the build worked.
* notify interested parties

As I understand it - that is about as basic as CI gets.

My build file runs like so:

D:\Builds\rake

 - that's on Windows 7 (64x) when I run it from the command line as
administrator
 - this build server is Windows 2008 R2.

I've tested that the build works on the server, when run by an
administrator.

The options for creating a new job in Jenkins seem overwhelming. I
have no idea what's essential, nor where the options are to do what I
want. E.g. Will Jenkins be able to copy the completed builds over to
the websites (over-writing any files along the way)?  Will I need to
create a new account to run Jenkins under? - giving it total control
over the build folders and websites? What happens when I start a job
and fail to finish it - do I delete it and start again or can I edit
it?  Does Jenkins store these jobs in configuration files, and, if so,
is it easier to just edit the config files to do what I want (as if it
were cruise control or Ant)?

Well, I realise that the people who wrote the Jenkins UI believe it to
be fool-proof ... but did they ever test it on naive users like me who
has no one here to help them? I'm just asking for the basic help to
get my primitive system working.

PS: emailing is disabled on this server - are there other notification
routes available to me? The good news is that I can see the Jenkins
website from my local box  http:/servername:8080/ - I guess that means
the crippled emailing notification is superfluous?



Reply via email to