On Fri, May 2, 2014 at 2:41 PM, John Park
<[email protected]> wrote:
>
> Ok, I think the slave node is properly being called to run the job as I see
> the message from the jenkins console output that it's delegating to the
> slave node using the label which I assigned.
>
> To answer your question about subversion, we are not using svn for this job.
> This job is simply to deploy our build to the slave windows environment
> using the provided ant script.There is a target in the ant script to copy
> the build files from our build machine and copy them over to the slave
> machine. So basically, all we want jenkins to do is execute our ant script
> which deploys our software. There's probably an easier way to do this in
> Jenkins, but since i've gone this far, i'd rather make it work via
> master/slave method now, haha.
Jenkins does have some of its own deployment concepts and plugins, but
it is good to get your own script working first. I'd still consider
sticking the build.xml in svn somewhere just to make sure it is always
up to date and appears in the right place since jenkins will take care
of that grunge work for you.
> You mention that if the build.xml is in the top level directory, an explicit
> path isn't needed in the job. By top level directory, do you mean
> C:/jenkins? or C:/jenkins/workspace/my_jenkins_job/ ?
C:/jenkins/workspace/my_jenkins_job/
You could have a lot of jobs, each with different build.xml files.
Also note that the C:/jenkins/ part is something you could change in
the node config.
> Thanks for hanging with me Les, I definitely owe you a beer...or 5.
No problem.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
